Why do we need framework?

• Maintainability:  How do we ensure maintenance of scripts is optimal?  By that we mean, as we evolve by churning out feature files, step definitions, data and page objects, we need to have a strategy to be able to diagnose, version control and audit the artifacts produced. There should also be a tight coupling between the released version of source code and the corresponding set of acceptance tests which tested that released version.

　　　　可维护性

• Re-usability: What are the specific artifacts that can be re-used across feature teams? This is particularly helpful during integration testing when components/functions have to talk to each other. For example, data and page objects are re-usable artifacts

　　　　可重用

• Scalability: How do we scale the acceptance tests and ultimately accelerate the feedback loop to verify/validate the software to release and market per deadlines?We can use Selenium GRID for parallel execution of tests. The necessary infrastructure required for a distributed parallel execution of tests needs to be discussed too. The technology needs for the same in the Technology section and any exceptions and dependencies on infrastructure (hardware/software) should be laid out.

　　　　可量测性

• Configurability: How do we configure the test automation framework and how much of it isconvention vs. configuration?Environment configuration (switch environments),Logging (Detailed log to help debug)

　　　　可置配性

• Auditability: How do we keep track of work done and roll up metrics to serve QS dashboards or any other management required metrics. Reports (Historical vs. current), Auditability (System of record

　　　　可审性