The description should be clear what the new functionality’s purpose is and what reaction in the application its use causes. ![]() Of course, there may be situations where the functionality is triggered by typing a command in the application, clicking on an icon, or similar. For me, the most helpful thing was usually the tab name and, for example, the full name of the button triggering the functionality. ![]() The exact application location/area in which the functionality is to operate.The person responsible for preparing the description is usually a Business Analyst or a Product Owner if the project is implemented in the Agile methodology. Test cases good quality and, consequently, functional tests’ correct execution depends on it. A correct description understandable for the tester is crucial.
0 Comments
Leave a Reply. |