Quality On Time - Distributed Requirements

Quality On Time

(Continued from previous question...)

Quality On Time - Distributed Requirements

• Scripts must retain independence from each other
  --If there are script dependencies, consider a 2-tier approach where at the "batch" tier (sometimes called Scenario) is independent, and all dependencies are handled within batch script
  
• Consider concurrent impact on data --Similar test cases require different input data to run on different machines simultaneously
  --Consider implementing machine-specific (C: drive) and machine-independent (LAN drive) data sources to feed data-driven tests
  
• Central Reporting Log (Cycle Execution Log) can be implemented to collect remote results of all machines in the test cycle

(Continued on next question...)

Other Interview Questions

• Quality On Time - verifiable levels of test coverage
• Quality On Time - A Closer Look at Test Frameworks
• Quality On Time - Strategic Considerations
• Quality On Time - Evaluation Criteria
• Quality On Time - Typical Framework Components
• Quality On Time - Team Skill Mix
• Quality On Time - A Closer Look at Team Skill Mix
• Quality On Time - Skill Mix: Impact on Framework
• Quality On Time - Number of Supported Applications and Releases
• Quality On Time - Anatomy of a Test Case
• Quality On Time - Maturity of Applications
• Quality On Time - A Closer Look at State Navigation
• Quality On Time - Unattended Requirements
• Quality On Time - Distributed Requirements
• Quality On Time - Miscellaneous