Shift Left Testing with DevSecOps
Abstract
The topic of this presentation is Shift-Left testing. Shift left testing requires: Practices and test tools, Timing of tests, Time to develop automate testing, Planning for testing (what and wow), Level of testing, and Culture change. It requires energy, commitment, resources and mindset. Different incremental approaches are: Single increment of work, delivered once in a single package, Single Delivery where work is divided into logical subsets for development in pieces to be delivered once in a single package, and Incremental development and delivery where the work is divided into meaningful slices of the total end result, delivered in gradually more complete versions, and alternatively, delivering new pieces rather than new versions. Capturing the right requirements is laid out with the anagram INVEST: Independent, Negotiable, Valuable, Estimable, Small and Testable. There is an explanation of the definitions of Ready and Done. Testing in General is discussed along with: test harness, test data, testing in development environment, functional testing, testing in continuous integration environment, testing in staging environment, user tests, performance tests, the test database, security testing, testing for embedded systems, development boards and prototypes, hardware simulation, and hardware-based testing with DevSecOps. Agile development and tests have inter-twingles, and agile iteration relies on more testing earlier. The presentation finished with Agile High Assurance Dev/Test cadence and Tools for Text Automation.
Document Details
- Document Type
- Technical Report
- Publication Date
- Jul 25, 2022
- Accession Number
- AD1174915
Entities
People
- Hasan Yaşar
Organizations
- Carnegie Mellon University