Skip to end of metadata
Go to start of metadata

Key milestones

Milestone Date
Iteration start 01.10.2012
Intermediate build – Regression testing 22.10.2012
Intermediate build – full BM data migration 26.10.2012
Intermediate build – Data basket 29.10.2012
Intermediate build - CRM Cookbook ?
Iteration final – Final testing RS3.5 31.10.2012
Responsible tester: Anna Radeva

*Web app server (Tomcat5): http://nuxeo.ontotext.com, installed at /nidata/nuxeo on local port 8081, user/pass: Administrator/Administrator or Ann/159357

NUXEO DM 5.4.3-I20111003_1046

Firefox 15.0.1 and Chrome 22.0.1229.79 m

User-interface (UI) testing

This type of tests will take place after each intermediate build, in order to maximize effectiveness and quality control.
Goal: Confirmation of the following parameters:
• System navigation corresponds to the business and process logic.
• All objects correspond to the standards, including menus, size, space and positioning.
Technique: The tests are executed for all screens, in order to confirm any misplacement on the screen, switch of objects and fields. Browsers with different cores are used – Internet Explorer and Mozilla Firefox.
Criteria for successful completion: Each screen corresponds to the standards, mocups and specifications.
No differences in the design, when using different browsers (Firefox 13.0.1 and Chrome 19.0.1084.56 m).
Responsible: Anna Radeva

 

Regression Testing

This type of tests will take place after each intermediate build, in order to maximize effectiveness and quality control.
Goal: Make sure that the implemented functionality and components of RS3.1, RS3.2, RS3.3 and RS3.4  are corrected. If they reappear, document them again.
  • Regression testing Search/Autocomplete
  • Regression testing Data annotation
  • Regression testing Image annotation
  • Regression testing Social Networking
Technique: Use and update the TCs previously created for the functional tests.
Criteria for successful completion: All planned and written TCs are executed.
All documented bugs/defects are retested. When bugs/defects reappear in the process of testing, they are documented anew.
Responsible: Anna Radeva

Functional testing

This type of tests will take place after each intermediate build is released, as per estimated dates, and will correspond to the implemented key functionality of RS3.5
Goal: To check all functionality and components of the system, according to the current specifications for RS3.5, regarding the complete functionality, including navigation, data entry, processes and their repetition.
Technique: Execution of the full set of written TCs, using valid and invalid data for each of the parameters, in order to be able to confirm:
• The expected results, when valid data (according to the functional specifications) is entered.
• The presence of informational message(s) and the overall system state when invalid/wrongly entered data is given.
• Components for testing:
  • Data Basket
  • BM data migration
  • CRM Cookbook
Criteria for successful completion: All planned and written TCs are executed.
All bugs/defects found in the process of testing are documented.
Responsible: Anna Radeva

Evaluation criteria

• Work functionality and components - planned compared to actually completed.
• 97% of test cases passed.
• Final build of iteration RS3.5 with all new functionality received favorable response.
• Favorable response to demo.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.