Exercise 8

1. complete

1. In test pyramid, (.....) and (.....) level tests are automated and created using (.....) tools. At (.....) and (.....) levels, automated tests are created using (.....) tools.
2. Testing quadrants apply to (.....) testing only.
3. (.....) strategies can be used by the testers in Agile teams to help determine the acceptable number of test cases to execute.
4. Iteration starts with iteration (.....) which ends in tasks on a task board. These tasks can be (.....) in part based on level of (.....) associated with them. The aim is to know which tasks should start (.....) and involve more (.....) effort.
5. During iteration planning, team assesses each identified risk, which includes two activities: (.....) and determining (.....) based on (.....) and (.....)
6. Information from the (.....) is used during poker planning sessions to determine priorities of items to be completed in the (.....)
7. The main part of the lifecycle cost often comes from (.....) .

1. (unit - integration - api based - system - acceptance - gui-based)
2. (dynamic)
3. (Risk identification, analysis, and risk mitigation)
4. (planning - prioritized -quality risks - earlier - testing)
5. (categorizing risks - its level of risk - impact - the likelihood of defects)
6. (risk analysis - iteration)
7. (maintenance after the product have been released)

2. replace with key terms

1. is the first iteration of the project where many preparation activities take place.
2. Each team member brings a different set of skills to the team. The team works together on test strategy, planning, specification, execution, evaluation, and results reporting.
3. The team may consist only of developers, ideally there would be one or more testers.
4. Testers sit together with the developers and the product owner.
5. Testers collaborate with team members (stakeholders, product owner, Scrum Master).
6. Technical decisions regarding design and testing are made by the team as a whole.
7. The tester is committed to question and evaluate the product’s behaviour and characteristics with respect to the expectations and needs of the customers and users.
8. Development and testing progress is visible on the Agile task board.
9. The tester must ensure the credibility of the strategy for testing, its implementation, and execution, otherwise the stakeholders will not trust the test results.
10. Retrospectives allow teams to learn from successes and from failures.
11. Testing must be able to respond to change, like all other activities in Agile projects.
12. Externally observable behaviour with user actions as input operating under certain configurations.
13. How the system performs the specified behaviour. Referred to as quality attributes or non-functional requirements.
14. A sequence of actions between an external actor (often a user) and the system, in order to accomplish a specific goal or business task.
15. Activities that can only be performed in the system under certain conditions defined by outside procedures and constraints.
16. Between system and outside world.
17. Design and implementation constraint that will restrict the options for the developer such as embedded software respecting physical constraints such as size, weight.
18. The customer may describe the format, data type, allowed values, and default values for a data item in the composition of a complex business data structure.
19. communication tool allows teams to build and share an online knowledge base on tools and techniques for development and testing activities.
20. are used to store source code and automated tests, manual tests and other test work products in same repository.
21. Tools that generate data to populate an application’s database are very beneficial when a lot of data and combinations of data are necessary to test the application.
22. Manual data entry is often time consuming and error prone, but data load tools are available to make the process reliable and efficient.
23. Specific tools are available to support test-first approaches, such as BDD, TDD, ATDD.
24. Tools capture and log activities performed on an application during an exploratory test session
25. how many defects are found per day or per transaction
26. number of defects found compared to number of user stories, effort, and/or quality attributes
27. provides the test conditions to cover during a time-boxed testing session.
28. uninterrupted period of testing, could last from 60-120 mints

1. Sprint zero
2. Cross functional
3. Self organizing
4. Co located
5. Collaborative
6. Empowered
7. Committed
8. Transparent
9. Credible
10. Open to feedback
11. Resilient
12. Functional behavior
13. Quality characteristics
14. Scenarios (use cases)
15. Business rules
16. External interfaces
17. Constraints
18. Constraints
19. Wikis
20. configuration management tools
21. Test data preparation and generation tools
22. Test data load tools
23. Automated test execution tools
24. Exploratory test tools
25. Defect intensity
26. Defect density
27. test charter
28. Session

3. Mention Test Quadrants

4. Agile Tester Skills

1. Competent in test automation, TDD, BDD, ATDD, white-box, black-box, experience testing.
2. positive and solution-oriented with team members.
3. Actively acquire information from stakeholders
4. Accurately evaluate and report test results.
5. Plan and organize their own work.
6. Respond to change quickly.
7. Collaborative.

5. Agile Tester Role

1. Understanding, implementing, and updating test strategy.
2. Measuring and reporting test coverage.
3. Ensuring proper use of testing tools.
4. Actively collaborating with developers and business stakeholders.
5. Reporting defects and working with the team to resolve them.
6. Participating in team retrospectives.

6. Mention Common estimation testing effort techniques used in Agile projects based on content and risk

1. planning poker.
2. T-shirt sizing.

7. Test sessions include

1. Survey session.
2. Analysis session.
3. Deep coverage.

8. Mention tools to support communication and information sharing

1. wikis.
2. instant messaging.
3. desktop sharing.

9. Tester role in scrum projects

1. Cross-functional
2. Self-organizing
3. Co-located
4. Collaborative
5. Empowered
6. Committed
7. Transparent
8. Credible
9. Open to feedback
10. Resilient

10. Activities of sprint zero

1. Identify the scope of the project
2. Create an initial system architecture
3. Plan, acquire, and install needed tools
4. Create an initial test strategy
5. Perform an initial quality risk analysis
6. Create the task board

11. Quality Risk Analysis During Iteration Planning

1. Gather the Agile team members together
2. List all the backlog items for the current iteration
3. Identify the quality risks
4. Assess each identified risk
   • categorizing the risk
   • determining its level of risk
5. Determine the extent of testing
6. Select the appropriate test technique(s) to reduce each risk
7. The tester then designs, implements, and executes tests to mitigate the risks.

12. Mention the topics that is addressed by acceptance criteria

1. Functional behavior
2. Quality characteristics
3. Scenarios
4. Business rules
5. External interfaces
6. Constraints
7. Data definitions

13. Mention uses of physical story/task boards in agile teams

1. Record stories
2. capture team members' estimates on there task and calculate efforts
3. Provide a visual representation
4. Integrate with configuration management tools

14. Benefits of desktop sharing and capturing tools

1. Used for distributed teams, product demonstrations, code reviews, and even pairing.
2. Capturing product demonstrations at the end of each iteration.

General Exercises

1. Complete

1. During exploratory testing, results of the most recent tests guide the (.....).
2. (.....) is an uninterrupted period of testing, could last from 60-120 mints.
3. Test sessions include (.....) session to learn how it works, (.....) session to evaluate functionality, and (.....) for corner cases, scenarios, and interactions.
4. (.....) provides a visual representation (via metrics, charts, and dashboards) of the current state of each user story, the iteration, and the release, allowing all stakeholders to quickly check status.
5. Some Agile teams opt for an all-inclusive tool called (.....) that provides relevant features (such as task boards, burndown charts, and user stories).
6. (.....) allow teams to build up an online knowledge base on tools and techniques for development and testing activities.
7. Risk of introducing regression in Agile development is high due to extensive (.....). To maintain velocity without incurring a large amount of (.....), it is critical that teams invest in (.....) at all test levels early.
8. It is critical that all test assets are kept up to-date with each (.....).
9. Testers need to allocate time in each (.....) to review manual and automated test cases from previous and current iterations to select test cases that may be candidates for the.
10. (.....), (.....), and (.....) are three complementary techniques in use among Agile teams for testing across various test levels.
11. Benefits of test-driven development include (.....), (.....), and (.....).
12. Results of BDD are (.....) used by the developer to develop test cases.
13. BDD is concerned primarily with the specification of the behavior of the system under test as a whole, thus suited for (.....) and (.....) testing.

1. (Test Creation)
2. (Session)
3. (Survey session - Analysis session - Deep coverage)
4. (physical story/task boards)
5. (test management tools)
6. (Wikis)
7. (code churn - technical debt - test automation)
8. (iteration)
9. (iteration)
10. (Test-driven development - behavior-driven development - acceptance test-driven development)
11. (Code coverage - Regression testing - Simplified debugging - System documentation)
12. (test classes)
13. (acceptance - regression )

2. Replace with Key Term(s)

1. Release that helps developer team and on-site customer to demonstrate product and focus only on least amount of work that has highest priority.
2. XP team is not doing actual development during this time but acts as a buffer to deal with uncertainties and issues.
3. Planning level where the requirements and features that can be delivered into production are decided based on priorities, capacity, estimations and risks factor of the team to deliver.
4. In Kanban, the amount of parallel active tasks is strictly limited. This is controlled by the maximum number of tickets allowed for a station and/or globally for the board.
5. Methodology used in situations where work arrives in an unpredictable fashion or when you want to deploy work as soon as it is ready, rather than waiting for other work items.
6. Need to integrate changes made every few hours or on a daily basis so after every code compilation and build we have to integrate it where all the tests are executed automatically for the entire project.
7. Testing technique creates a functional/behavioral test for a requirement that fails because the feature does not exist.
8. Testing technique where stakeholders write acceptance tests in plain language based on shared understanding of user story requirements.
9. Common effort estimation technique used in Agile projects.
10. Technique used by testers to write effective user stories and maintain collaborative authorship.
11. Testing where test design and test execution occur at the same time, guided by a prepared test charter.
12. Chart represents the amount of work left to be done against time allocated to the release or iteration.
13. Testing adequate in Agile projects in case of limited time available for test analysis and limited details of the user stories.
14. Capture story cards, development tasks, test tasks created during iteration planning, using color-coordinated cards.
15. Is the software product easy to use, learn and understand from the user’s perspective?
16. The effort needed to make specified modifications. Is the software product easy to maintain?
17. The relationship between the level of performance of the software and the amount of resources used, under stated conditions. Does the software product use the hardware,system software and other resources efficiently?
18. It refers to the validation of the documents and specifications on which test cases are designed.
19. The ability of software to be transferred from one environment to another. Is the software product portable?
20. The ability to interact with specified systems. Does the software product work with other software applications, as required by the users?
21. checking default languages, currency, date, and time format if it is designed for a particular region/locality.
22. It is done in order to check how fast and better the application can recover after it has gone through any type of crash or hardware failure.

1. Minimum Viable Product (MVP)
2. Slack time
3. release planning
4. Work-in-Progress WIP Limit
5. Kanban
6. Continuous Integration (CI)
7. BDD
8. ATDD
9. planning poker and T-shirt sizing
10. INVEST Technique
11. Exploratory testing
12. burndown charts
13. Exploratory testing
14. Agile Task Board
15. Usability
16. Maintainability
17. Efficiency
18. Baseline
19. Portability
20. Interoperability
21. Localization
22. Recovery

3. What does collective code ownership mean?

Success or failure is a collective effort and there is no blame game. There is no one key player here, so if there is a bug or issue then any developer can fix it.

4. List categories of project work products of interest to Agile testers. Mention one example on each category.

1. Business-oriented work products

   requirements specifications/user stories

2. Development work products

   database ERD , code , unit tests

3. Test work products

   test strategies and plans , manual and automated tests

5. In a typical Agile project, it is a common practice to avoid producing vast amounts of documentation. Comment.

• focus is more on having working software, together with automated tests that demonstrate conformance to requirements.
• This encouragement to reduce documentation applies only to documentation that does not deliver value to the customer.

6. Differentiate between lead and cycle times

• lead time : is the time between a request being made and a task being released.
• cycle time : is calculating the actual work-in-progress time

7. Automated acceptance tests are run with each check-in. True/False?

False

8. In addition to test automation, other testing tasks may also be automated. Mention three.

1. Test data generation
2. Loading test data into systems
3. Deployment of builds into the test environments
4. Restoration of test environment to a baseline
5. Comparison of data outputs

9. Differentiate between defect density and intensity.

• Defect intensity : how many defects are found per day or per transaction
• Defect density : number of defects found compared to number of user stories, effort, and/or quality attributes

10. List four items included in wikis

1. Product feature diagrams, feature discussions
2. Tools and techniques
3. Metrics, charts, and dashboards
4. Conversations

11. Identify Corresponding Test Level ” Done”

1. All user personas covered.
2. All interfaces between units tested.
3. 100% decision coverage, if possible, with careful review of infeasible paths.
4. All constituent user stories, with acceptance criteria, are approved by customer.
5. Testing done in a production-like environment(s).
6. All features for the iteration are ready and individually tested according to the feature level criteria.

1. System testing.
2. Integration testing.
3. Unit testing.
4. Feature testing.
5. System testing.
6. Iteration testing.

12. Identify Test Tool

1. Tools used to replace manual data loading.
2. Specific tools available to support test first approaches, such as behavior-driven development, test-driven development, and acceptance test-driven development.
3. Tools used to populate an application’s database are very beneficial when a lot of data and combinations of data are necessary to test the application.
4. Tools capture and log activities performed on an application during an exploratory test session.

1. Test data load tools.
2. Automated test execution tools.
3. Test data preparation and generation tools.
4. Exploratory test tools.