IS480 Team wiki: 2013T2 SkyTeam User Testing
Use Case Design | Architecture Design | Prototypes | Testing | Presentation Materials |
Testing Strategy
System will be continually tested throughout the entire development phase. While all coders are responsible to test a function locally, a member (Edric) is specifically assigned to perform full system testing after it is deployed. Specific time frames have been set aside for dedicated testing purposes. Bug metrics and Test metrics will be updated consistently throughout development phase. The list of development phases, with the platforms they are performed and resouceres allocated for each are specified below:
Approach
There are 5 different testing types that we will conduct during the testing phase. From the list below, 1 – 4 will be done at every end of iteration internally and 5, user testing, will be done at a specific period of time assigned in the project schedule.
1. Component Testing
This testing is conducted to verify the implementation of one specific software element that is just deployed at the current iteration. The purpose of component testing is to ensure that the program logic is complete and correct and ensuring that the component works as designed.
2. Regression Testing
This testing is done to ensure that the applied changes or the added functionalities to the system does not adversely affect previously tested functionality.
3. Integration Testing
This testing conducted in which all application elements are combined and tested until the entire system has been integrated. The purpose of integration testing is to ensure that design objectives are met and ensures that the software, as a complete entity, complies with operational requirements.
4. Interface & Performance Testing
This testing examines if all interface elements and systems comply to how they are designed and if the system delivers result as alligned to the quality customers expected (response time, availability, usability). This testing ensure that application is users friendly and efficient.
5. User Testing
This testing is conducted with sponsors most importantly clients from the insurance companies to determine whether the system satisfies the acceptance criteria. User testing ensures that customer requirements' objectives are met and that all components are correctly included in a customer package. The testing will include interviews and surveys. Followings are the planned iterations and features to be tested:
Testing Process
Test Deliverables:
During the execution of test cases at the end of iteration, the following documents must be updated:
- Test cases will be recorded accordingly and committed onto repository so that everyone is updated.
- Test metrics will be updated to measure the quality of the software under the test and the effectiveness of the testing activities.
- Bug metrics will be updated to include bugs uncovered during testing period.
Responsibilities:
Results
UT1, UT 2 & UT3 Feedback Scores
UT1, HE1 & UT 2 Summarised Comments
UT1, HE1 & UT 2 Changes
UT3 Changes