Foundation Level 2

Question 1

A software development lifecycle (SDLC)

Answer 1

1. an abstract, high-level representation of the software development process
2. defines how different development phases and types of activities performed within this process relate to each other, both logically and chronologically

Question 2

Examples of SDLC models

Answer 2

1. sequential development models (e.g., waterfall model, V-model),
2. iterative development models (e.g., spiral model, prototyping)
3. incremental development models (e.g., Unified Process)

Question 3

Impact of the Software Development Lifecycle on Testing

Answer 3

1. Scope and timing of test activities (e.g., test levels and test types)
2. Level of detail of test documentation
3. Choice of test techniques and test approach
4. Extent of test automation
5. Role and responsibilities of a tester

Question 4

Good testing practices, independent of SDLC model

Answer 4

1. For every software development activity, there is a corresponding test activity => quality control
2. Different test levels have specific and different test objectives => comprehensive, no redundancy
3. Test analysis and design for a given test level begins during the corresponding development phase of the SDLC => principle of early testing
4. Testers are involved in reviewing work products as soon as drafts of this documentation are available => supports shift left

Question 5

Testing as a Driver for Software Development (Approaches)

Answer 5

1. Test-Driven Development (TDD)
2. Acceptance Test-Driven Development (ATDD)
3. Behavior-Driven Development (BDD)

Question 6

Test-Driven Development (TDD)

Answer 6

1. Directs the coding through test cases
2. Tests are written first, then the code is written to satisfy the tests
3. The tests and code are refactored

Question 7

Acceptance Test-Driven Development (ATDD)

Answer 7

1. Derives tests from acceptance criteria as part of the system design process
2. Tests are written before the part of the application is developed to satisfy the tests

Question 8

Behavior-Driven Development (BDD)

Answer 8

1. Expresses the desired behavior of an application with test cases written in a simple form of natural language, which is easy to understand by stakeholders – usually using the Given/When/Then format.
2. Test cases are then automatically translated into executable tests

Question 9

Challenges & Risks of DevOps (test design perspective)

Answer 9

1. The DevOps delivery pipeline must be defined and established
2. CI / CD tools must be introduced and maintained
3. Test automation requires additional resources and may be difficult to establish and maintain

Question 10

Benefits of DevOps for testing

Answer 10

1. Fast feedback on the code quality, and whether changes adversely affect existing code
2. CI promotes a shift-left approach in testing by encouraging developers to submit high quality code accompanied by component tests and static analysis
3. Promotes automated processes like CI/CD that facilitate establishing stable test environments
4. Increases the view on non-functional quality characteristics
5. Automation through a delivery pipeline reduces the need for repetitive manual testing
6. The risk in regression is minimized due to the scale and range of automated regression tests

Question 11

Shift-Left Approach

Answer 11

1. an approach where testing is performed earlier in the SDLC
2. it does not mean that testing later in the SDLC should be neglected.
3. the process but is expected to save efforts and/or costs later in the process.

Question 12

Good practices that illustrate how to achieve a “shift-left” in testing,

Answer 12

1. Reviewing the specification from the perspective of testing. These review activities on specifications often find potential defects, such as ambiguities, incompleteness, and inconsistencies
2. Writing test cases before the code is written and have the code run in a test harness during code implementation
3. Using CI and even better CD as it comes with fast feedback and automated component tests to accompany source code when it is submitted to the code repository
4. Completing static analysis of source code prior to dynamic testing, or as part of an automated process
5. Performing non-functional testing starting at the component test level, where possible. This is a form of shift-left as these non-functional test types tend to be performed later in the SDLC when a complete system and a representative test environment are available

Question 13

Benefits of retrospectives for testing include

Answer 13

1. Increased test effectiveness / efficiency
2. Increased quality of testware
3. Team bonding and learning
4. Improved quality of the test basis
5. Better cooperation between development and testing

Question 14

Hot fix

Answer 14

unplanned releases/deployments

Question 15

Categories of maintenance

Answer 15

1. Corrective
2. Adaptive to changes
3. Improve performance or maintainability

Question 16

Testing the changes to a system in production includes:

Answer 16

1. evaluating the success of the implementation of the change
2. the checking for possible regressions in parts of the system that remain unchanged

Question 17

The scope of maintenance testing depends on

Answer 17

1. The degree of risk of the change
2. The size of the existing system
3. The size of the change

Question 18

The triggers for maintenance and maintenance testing can be classified as

Answer 18

1. Modifications, such as planned enhancements (i.e., release-based), corrective changes or hot fixes.
2. Upgrades or migrations of the operational environment, such as from one platform to another, which can require tests associated with the new environment as well as of the changed software, or tests of data conversion when data from another application is migrated into the system being maintained.
3. Retirement, such as when an application reaches the end of its life. When a system is retired, this can require testing of data archiving if long data-retention periods are required.

Question 19

Confirmation testing

Answer 19

confirms that an original defect has been successfully fixed.

Question 20

Regression testing

Answer 20

1. confirms that no adverse consequences have been caused by a change, including a fix that has already been confirmation tested.
2. Regression testing may not be restricted to the test object itself but can also be related to the environment
3. It is advisable first to perform an impact analysis to optimize the extent of the regression testing. Impact analysis shows which parts of the software could be affected.

Question 21

Test levels: definition

Answer 21

1. groups of test activities that are organized and managed together
2. an instance of the test process, performed in relation to software at a given stage of development,

Question 22

Test types

Answer 22

1. groups of test activities related to specific quality characteristics
2. most of those test activities can be performed at every test level.

Question 23

Test levels example

Answer 23

1. Component testing
2. Component integration testing
3. System testing
4. System integration testing
5. Acceptance testing

Question 24

Component testing

Answer 24

1. components in isolation
2. normally performed by developers in their development environments

Question 25

Component integration testing

Answer 25

1. testing the interfaces and interactions between components 2. heavily dependent on the integration strategy approaches like bottom-up, top-down or big-bang

Question 26

System testing

Answer 26

overall behavior and capabilities of an entire system or product, often including functional testing of end-to-end tasks and the non-functional testing of quality characteristics NB using simulation of sub-systems is possible

Question 27

System integration testing

Answer 27

focuses on testing the interfaces of the system under test and other systems and external services . System integration testing requires suitable test environments preferably similar to the operational environment

Question 28

Acceptance testing

Answer 28

validation and on demonstrating readiness for deployment, which means that the system fulfills the user’s business needs. NB ideally be intended users

Question 29

The main forms of acceptance testing

Answer 29

1. user acceptance testing (UAT) 2. operational acceptance testing 3. contractual and regulatory acceptance testing 4. alpha testing and beta testing.

Question 30

Test levels are distinguished by the following non-exhaustive list of attributes

Answer 30

1. Test object 2. Test objectives 3. Test basis 4. Defects and failures 5. Approach and responsibilities

Question 31

Test Types

Answer 31

1. functional testing 2. non-funcional testing 3. black box testing 4. white box testing

Question 32

Functional testing

Answer 32

evaluates the functions that a component or system should perform. The main objective - checking the functional completeness, functional correctness and functional appropriateness.

Question 33

Non-functional software quality characteristics

Answer 33

1. Performance efficiency 2. Compatibility 3. Usability 4. Reliability 5. Security 6. Maintainability 7. Portability