The DevOps Handbookto run in parallel ii. Enable different test categories to run in parallel iii. Generally, limit manual testing if automated tests haven’t passed iv. For resource intensive suites, performance tests, new and old code to make it well structured” j. AUTOMATE AS MANY OF OUR MANUAL TESTS AS POSSIBLE i. Reduce the reliance on manual testing ii. Elisabeth Hendrickson – “Although testing can be automated features, 20% on detailed planning, 25% on porting code amongst branches, 10% integrating, 15% manual testing. ii. Implemented Trunk-based development & CI iii. After CI: 40% effort on new features0 码力 | 8 页 | 23.08 KB | 5 月前3
The DevOps HandbookDOING MORE MANUAL TESTING AND CHANGE FREEZES i. When testing failures occur, adding more testing could backfire, especially if the testing is at the end of a project and/or manual 1. Manual testing is0 码力 | 8 页 | 24.02 KB | 5 月前3
MITRE Defense Agile Acquisition Guide - Mar 20148.1.1 IT Box The Joint Requirements Oversight Council (JROC) published an update to the JCIDS Manual on 19 Jan 12 that includes an IT Box model for Information Systems (IS). The policy applies to programs four sides of the IT Box identified in the IS-ICD include: Figure 12 IT Box (Source JCIDS Manual 19 Jan 12) As long as the program operates within these four sides of the IT Box, they need not must also be flexible.22 Figure 13: Example of Requirements Documentation (Data Source: JCIDS Manual) 8.1.2 Aligning IT Box Requirements to Agile Development The IS ICD provides an initial requirements0 码力 | 74 页 | 3.57 MB | 5 月前3
The DevOps HandbookExtra features: d. Task switching: e. Waiting: f. Motion: g. Defects: h. Nonstandard or manual work:i. Heroics: d. The Second Way: The Principles of Feedback 27 i. KEEP PUSHING QUALITY CLOSER ineffective quality controls include: a. Requiring another team to complete tedious, error-prone, and manual tasks that could be easily automated and run as needed by the team who needs the work performed0 码力 | 8 页 | 22.57 KB | 5 月前3
DoD CIO Enterprise DevSecOps Reference Design - SummaryPrinciples to implementing a successful DevSecOps approach Remove bottlenecks (including human ones) and manual actions. Automate as much of the development and deployment activities as possible. Adopt common0 码力 | 8 页 | 3.38 MB | 5 月前3
The Goal - A Process of Ongoing Improvementbottleneck, you have lost time that cannot be recovered.” Parallel: Automated Unit Testing before Manual Testing & QA Time and Batch sizes From the moment material comes into the plan to the minute0 码力 | 6 页 | 100.81 KB | 5 月前3
The DevOps HandbookCATEGORIZED AS NORMAL CHANGES i. If change approval board is required, aim for quick deployment even if manual steps are required ii. Use tooling to generate the artifacts needed for approval. Share evidence0 码力 | 9 页 | 25.13 KB | 5 月前3
共 7 条
- 1













