2.1 Testing in the SDLC Flashcards
How does the choice of SDLC model impact testing?
- scope and timing of test activities
- level of detail in test docs
- choice of test techniques and approach
- Extent of test automation
- role and responsibilities of a tester
How do sequential development models (Waterfall) affect testing?
In early phases, testers participate in requirement reviews, test analysis, and test design.
Dynamic testing cannot be performed until later in the SDLC when executable code has been created.
How do iterative development models (Agile) affect testing?
When each iteration delivers a working prototype or product increment, both static and dynamic testing may be performed at all test levels for each iteration.
Frequent delivery requires fast feedback and extensive regression testing.
How does an Agile SDLC affect testing?
We assume change may occur throughout the project. Therefore we favor:
- lightweight documentation
- extensive automation of regression testing
- manual testing based on experience-based test techniques
What are good testing practices regardless of SDLC?
- For every development activity, there is a corresponding test activity
- Different test levels have specific and different test objectives, to be comprehensive but not redundant
- Test analysis and design for a given test level begins during the corresponding development phase
- Testers are involved in reviewing work products as soon as drafts of the docs are available (shift-left)
Describe Test-Driven Development
- directs coding through test cases (instead of extensive software design)
- tests are written first, then code is written to satisfy tests, then both are refactored
Describe Acceptance-Test Driven Development
- derives tests from acceptance criteria as part of system design process
- otherwise, the same as TDD
Describe Behavior-Driven Development
- expresses the desired behavior of an application with test cases written in a simple form of natural language, easy to understand by stakeholders
- usually using the Given / When / Then format
- test cases are then (automatically) translated into executable tests
What is DevOps?
An organizational approach that creates synergy by getting development and operations teams to work together to achieve a set of common goals. Testing is included on the dev side.
From the perspective of testing, what are some benefits of DevOps?
- fast feedback on code quality
- encourages developers to submit high quality code accompanied by component (unit) tests and static analysis
- promotes automated processes like CI/CD
- Increased view on non-functional quality like performance and reliability
- Automation through delivery pipeline reduces need for repetitive manual testing
- Risk in regression is minimized due to scale and range of automated regression tests
What are three risks or challenges of DevOps?
- the DevOps delivery pipeline must be defined and established
- CI / CD tools must be introduced and maintained
- Test automation requires additional resources and may be difficult to establish and maintain
What is meant by a shift-left approach?
Testing should be started earlier in the SDLC, not waiting for code to be fully implemented or components to be integrated.
Describe good practices to “shift-left”.
- Review specifications from a test perspective.
- Write test cases before code is written and test as it is implemented.
- Use continuous integration and continuous delivery to get fast feedback.
- Complete static code analysis before dynamic testing, or via automation.
- Start non-functional tests at the component level instead of waiting to do it later.
How does a shift-left approach affect efforts and costs?
It requires additional upfront effort and cost, but saves you time and money down the road.
What is discussed in a Retrospective?
What was successful and should be retained?
What was not successful and could be improved?
How can we do these things in future projects?
