Quality On Time - Skill Mix: Impact on Framework

Quality On Time

(Continued from previous question...)

Quality On Time - Skill Mix: Impact on Framework

• Strive for the simplest scripting environment possible
  --Move all complexities to the Developer/Guru
  --Gated by the skills of the Developers/Gurus
  
• Open Architecture allows tremendous flexibility in customization
  
• Hide as much of the complexity of the framework as possible
  --Automatically load harness components at tool load time
  --Incorporate routine maintenance and special reporting needs into simple function calls
  
• Consider the maintainability and simplicity of the framework itself when making enhancements to it

(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