Page Comparison

RMsis provides a basic From RMsis 1.4.0 onwards, Test Cases functionality has undergone significant changes with the introduction of versions control and concept of Test Runs (Test Execution Cycle).

RMsis provides functionality to specify and map test cases to requirements as well as to maintain an oversight of the product releases from testing perspective. The basic purpose of providing Test Case functionality in RMsis is to:

1. ensure that the defined test cases are sufficient to cover the requirement specifications.
2. get a comprehensive view of the test execution and identify the specifications having implementation issues.

The following are non-objectives for Test Case functionality, as far as RMsis is concerned

1. Test Case design and development.

Overall the validation functionality Requirements Validation Functionality is split between Test Cases, and Test Cycles and Views as follows:

• Test Cases is all about managing the lifecycle of an individual "Test Case". Following are key operations supported with Test Cases :-
  
  • Manage
    
    • Create
    • Update
    • Delete
  • Import
  • Export
  • Version Control
  • Commit
  • Filtered Views
• Test CyclesTest Runs is about managing the lifecycle of a specific "Test Run". Following are key operations supported with Test Cases :-
  
  • Manage
    
    • Create / Define
    • Update
    • Delete
    • Commit & Archive
    • Save As (Export)
  Views
  
  • Default
  • Filtered View using
  • Test Cycles
  • Baselines
  ReleasesImport
  • Export
  • Commit
  • Copy
  • Filtered Views
• Views
  
  • The two views (Test Cases / Test Runs) are presented in different tabs, so that both Test Case developers and Testers get a relevant context.