-------------------------------------------------
Defects mean rework, rework mean waste
Effective quality control measures:
n accurate and complete description of user needs
n focus on non-functional requirements
n quality built-in development process
n small cycles fast acquisition verification feedback
n automation, automation, automation
n open and transparent information, authorization decisions
n appropriate architecture, organizational architecture and match
n learn from failure
--------------------------------------------------------------------------
Test pyramid and tested by wound
Code -> Unit Test -> Integration Testing -> interface test -> UI / Function Testing -> production deployment
unit test
n automatic / manual
The n IDE / pipelined execution
n file to execute a single code
n the need to deploy
speed n
n Responsibilities: Developer
n Tools: junit test frameworks
Integration Testing:
n automatic / manual
The n IDE / pipelined execution
n single / multiple code file to execute
n may want to deploy
n faster
n Responsibilities: Developer
n Tools: based on the test frame or manually
Interface Test:
n automatic / manual
n particular execution environment
n single service is deployed (microService)
n need to deploy
n slow
n Responsibilities: Development / testers
n Tools:
UI / functional test:
n automatic / manual
n particular execution environment
n Complete system deployment is complete
n need to deploy
n Slow
n Responsibilities: Development / testers
n tool, Selenium
Automated testing is a condition some type of test
Unit Testing: you do not need to be able to test in the deployment environment
Pyramid and test the software life cycle:
---------------------------------------------------------------------
Evolution of Microsoft's test management strategy
L0: Every time embedded run-time files only need to run, run CI must be fast and reliable
L1: each insert, but relies on environmental resources
L2: we must address the specific "environment running, gradually clean up"
L3: run directly in a production environment
in principle:
n test application code is written at the lowest level
n Write once, can run in all environments (including production)
n can be an important goal of the design for testability thing
n test code as part of the production code, only test code can be retained stable operation
n micro test provides shared resources obtained automatically
Research and development to enhance the performance of the core Cheats
Management particle size: the DevOps from a management point it is always optimized by controlling the particle size "snap" to complete. The so-called "snap-in" may be a team, requirements, tasks, test, delivery of managed objects in any research and development, etc.
R & D performance improvements: Whether it is agile, lean or continuous delivery, its ultimate goal is to improve performance. The ability to so-called "performance" is the amount of output (efficiency) unit of input and organizations to achieve goals
Project decoupling: DevOps optimization from a technical point of it forever by decouple "Project object" to achieve. The so-called "engineering object" may be systems, tools, code, modules, services, adding, cloud or any object exists or delivery technology in the development process.