Skip to content

Refactoring test names for better documentation #19

@kishaningithub

Description

@kishaningithub

I see tests as a behavior documentation of the method under test. Currently i see tests of the name Test1, Test2,Test3 etc the intent of which is only understood upon reading the test itself.

I propose refactoring the test names to better describe the scenario that is being tested.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions