ISTQB Agile Tester Extension Exam Theory Study Material Part 14
Have a deep study of this entire question bank containing theory portion with detailed explanation. This study resource is as per the latest syllabus.
Just 1 hr. of time spent in brushing up your knowledge just before the ISTQB Agile Tester Extension Exam shall be of great help in clearing it.
Set of 10 Questions (Q. 131 to 140) with detailed explanation
Q. 131: What sort of questions are asked by testers during exploratory testing?
1) What is most important to find out about the system?
2) In what way may the system fail?
3) What happens if…..?
4) What should happen when…..?
5) Are customer needs, requirements, and expectations fulfilled?
6) Is the system possible to install and remove if necessary in all supported upgrade paths?
<<<<<< =================== >>>>>>
Q. 132: What essential skills are required in a tester performing exploratory testing?
1) Good knowledge and understanding of the software under test
2) Good knowledge and understanding of the business domain
3) Good knowledge and understanding of how the software is used
4) Good knowledge and understanding of when the system fails
5) Skill to find possible problems with the product
6) Creativity, intuition, cognition during test execution
<<<<<< =================== >>>>>>
Q. 133: What heuristics can be applied during testing?
Heuristics guide the tester in how to perform the testing and to evaluate the results
Examples of Heuristics are;
1) Boundaries
2) CRUD – means Create, Read, Update, Delete
3) Configuration variations
4) Interruptions like log off, shut down, or reboot
<<<<<< =================== >>>>>>
Q. 134: What information needs to be included in the testing process document?
A documented process is useful to the tester in going back and sees how a problem in the system was discovered.
List of information which is useful to be documented is:
1) Test coverage:
What input data have been used, how much has been covered, and how much remains to be tested
2) Evaluation notes:
Observations during testing, do the system and feature under test seem to be stable, were any defects found, what is planned as the next step according to the current observations, and any other list of ideas
3) Risk/strategy list:
Which risks have been covered and which ones remain among the most important ones, will the initial strategy be followed, does it need any changes
4) Issues, questions, and anomalies:
Any unexpected behaviour, any questions regarding the efficiency of the approach, any concerns about the ideas/test attempts, test environment, test data, misunderstanding of the function, test script or the system under test
5) Actual behaviour:
Recording of the actual behaviour of the system that needs to be saved (e.g., video, screen captures, output data files)
<<<<<< =================== >>>>>>
Q. 135: What tools are used in Agile Projects?
All tools used in traditional projects are relevant and used by testers on Agile teams.
1) Test management tools
2) Requirements management tools
3) Incident management tools or defect tracking tools
4) An all-inclusive tool like application lifecycle management or task management tool
5) Configuration management tools
<<<<<< =================== >>>>>>
Q. 136: What is the purpose of Task Management and Tracking Tools used by Agile teams?
1) Record stories and their relevant development and test tasks, to ensure that nothing gets lost during a sprint
2) Capture team members’ estimates on their tasks and automatically calculate the effort required to implement a story, to support efficient iteration planning sessions
3) Associate development tasks and test tasks with the same story, to provide a complete picture of the team’s effort required to implement the story
4) Aggregate developer and tester updates to the task status as they complete their work, automatically providing a current calculated snapshot of the status of each story, the iteration, and the overall release
5) Provide a visual representation (via metrics, charts, and dashboards) of the current state of each user story, the iteration, and the release, allowing all stakeholders, including people on geographically distributed teams, to quickly check the status
6) Integrate with configuration management tools, which can allow the automated recording of code check-ins and builds against tasks, and, in some cases, automated status updates for tasks
Some of the Agile teams also use:
# Physical story/task boards like a whiteboard, corkboard to manage and track user stories, tests, and other tasks throughout each sprint.
# Application lifecycle management and task management software, including electronic task boards.
<<<<<< =================== >>>>>>
Q. 137: What Communication and Information Sharing Tools are used by the Agile teams?
1) Wikis
2) Instant messaging
3) Desktop sharing
4) e-mail / documents
5) Verbal communication
<<<<<< =================== >>>>>>
Q. 138: What is the purpose of Wikis used by Agile teams?
Wikis help teams in building and sharing an online knowledge base on following aspects of the agile project:
1) Product feature diagrams, feature discussions, prototype diagrams, photos of whiteboard discussions, and other information
2) Tools and/or techniques for developing and testing found to be useful by other members of the team
3) Metrics, charts, and dashboards on product status, which is especially useful when the wiki is integrated with other tools such as the build server and task management system since the tool can update product status automatically
4) Conversations between team members, similar to instant messaging and email, but in a way that is shared with everyone else on the team
<<<<<< =================== >>>>>>
Q. 139: What are the benefits of instant messaging, audio teleconferencing, and video chat tools used by Agile teams?
1) Allow real-time direct communication between team members, especially distributed teams
2) Involve distributed teams in stand-up meetings
3) Reduce telephone bills by use of voice-over-IP technology, removing cost constraints that could reduce team member communication in distributed settings
<<<<<< =================== >>>>>>
Q. 140: What are the benefits of desktop sharing and capturing tools used by Agile teams?
1) In distributed teams, product demonstrations, code reviews, and even pairing can occur
2) Capturing product demonstrations at the end of each iteration, which can be posted to the team’s wiki
ISTQB Agile Tester Extension Exam Theory Study Material Part 15
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.