Analysis of Software Testing and Usability Testing Report

This report presents an overview of software testing and usability testing. It outlines the importance of testing, emphasizing the identification of weaknesses and the verification of software requirements. The report includes the process of test planning, from reviewing basic needs to defining test environments and metrics. It also details different types of usability testing, such as design walkthroughs, formative, and summative testing. The report provides a focus on performance metrics, including task success, task time, and error analysis, while also mentioning the questions used in a survey to analyze user behavior and design effectiveness. The report summarizes the importance of the testing process for software development.

1. Test plan
Test planning process
step1: Review and then analyse the basic needs of project
step2: the scope of testing by considering each and every activity
step3: Design out the strategy of test based on the scope
step4: identify and examine the tools that are needed for the process of testing and for managing
purpose
Step5: estimate the efforts made by team
step6: test schedule has to be defined with the help of assigned testers
step7: enhancement plan has to made
step8: determine the test environment by initiating the requests
step9: test metrics needs to be identified.
the above has to be done by the testers
Importance of testing
1) Testing identifies the weakness and strengths

2) verifies the software requirements
3) effective testing determines software testing appears to be performing according to the
requirements
2. set of tests (at least 5) to apply qualitative usability testing
The qualitative testing can be applied by the following
Design walkthrough- this is conducted during the prototype development process for validating
the initial designs and the decisions in addition with determining the strength and its weakness.
Formative usability testing- the design and the development phase helps in determining the
objective of the design.
Summative usability testing- the conducted test is to validate the product and is accomplished.
Performance metrics
Usability findings based on the behavior of user
Task success – this should have a clear end state
Task time- task time has to be noiticed for repetitive tasks
Errors: the incorrect actions leads to time loss
4 Questions taken up for survey
Based on the usability test, the analyses are made and the questions are taken for survey.
1) Which design meets the expectations?
2) Can user find the appropriate point?
3) Which part gives efficiency?
4) Which part takes more task time?