ISTQB Foundation Level Agile Tester - Extension. Ctfl-at: Chapter 1

1. Is the following statement true of false? While having contracts with customers may be important, working in regular and close collaboration with them is likely to bring more success to the project.

True

False

Customer often find great difficulty in specifying the system that they require.

Explanation

Customer often find great difficulty in specifying the system that they require.

2. In an Agile project, why individual and interaction is better than process and tools?

It is expensive to implement process and tools in an agile environment.

Developers, testers and Business representative do not like to use tools and they never follow processes.

None of the above is correct

It is through continuous communication and interaction that team can work most effectively

Explanation

It is through continuous communication and interaction that team can work most effectively

3. According to Scrum, math the following roles.

A coach ensuring that Scrum practices and rules are implemented

Represents the customer and generates prioritized product backlog

Develop and test the product, self-organized

Submit

4. What is the highest priority according to the twelve principles of the core Agile Manifesto values?

Finding bugs and fixing them

Always attend the daily stand up meetings

Reprimand testers who are unable to find large number of bugs

Satisfy customer through early and continuous delivery of valuable software

First principle of core agile value

Explanation

First principle of core agile value

5. One way to provide rapid feedback is by continuous integration

True

False

Continuous integration is a software development practice where developers frequently merge their code changes into a central repository, which triggers an automated build and test process. This process allows for rapid feedback as any issues or conflicts can be identified and resolved quickly. By continuously integrating code changes, teams can catch and address problems early on, leading to faster development cycles and improved software quality. Therefore, the statement that continuous integration is one way to provide rapid feedback is true.

Explanation

Continuous integration is a software development practice where developers frequently merge their code changes into a central repository, which triggers an automated build and test process. This process allows for rapid feedback as any issues or conflicts can be identified and resolved quickly. By continuously integrating code changes, teams can catch and address problems early on, leading to faster development cycles and improved software quality. Therefore, the statement that continuous integration is one way to provide rapid feedback is true.

6. Successful teams have been observed with as few as three people and as many as nine.

True

False

Successful teams can vary in size, but they have been observed to be effective with as few as three people and as many as nine. This suggests that the number of team members does not necessarily determine the team's success. Other factors such as communication, collaboration, and individual skills and strengths are likely to play a more significant role in determining the team's success. Therefore, it is true that successful teams can exist with a range of three to nine members.

Explanation

Successful teams can vary in size, but they have been observed to be effective with as few as three people and as many as nine. This suggests that the number of team members does not necessarily determine the team's success. Other factors such as communication, collaboration, and individual skills and strengths are likely to play a more significant role in determining the team's success. Therefore, it is true that successful teams can exist with a range of three to nine members.

7. What are the common practices across most of the agile practices?

Collaborative user story creation

Retrospective

Continuous integration

Release and iteration planning

All of the above

None of the above

The common practices across most of the agile practices include collaborative user story creation, retrospective, continuous integration, and release and iteration planning. These practices focus on involving the entire team in creating user stories, reflecting on the process and making improvements during retrospectives, integrating code frequently to ensure early detection of issues, and planning releases and iterations to prioritize and deliver value incrementally.

Explanation

The common practices across most of the agile practices include collaborative user story creation, retrospective, continuous integration, and release and iteration planning. These practices focus on involving the entire team in creating user stories, reflecting on the process and making improvements during retrospectives, integrating code frequently to ensure early detection of issues, and planning releases and iterations to prioritize and deliver value incrementally.

8. The Kanban process allows releasing its deliverables item by item, rather than as part of a release. Is the above statement true or false?

True

False

The statement is true. The Kanban process is a lean project management approach that focuses on visualizing work, limiting work in progress, and optimizing flow. One of the key principles of Kanban is to release deliverables item by item, rather than waiting for a complete release. This allows for faster feedback, shorter lead times, and the ability to prioritize and adjust work based on customer needs.

Explanation

The statement is true. The Kanban process is a lean project management approach that focuses on visualizing work, limiting work in progress, and optimizing flow. One of the key principles of Kanban is to release deliverables item by item, rather than waiting for a complete release. This allows for faster feedback, shorter lead times, and the ability to prioritize and adjust work based on customer needs.

9. During the creation of a user story, business representative stated that the profile creation form must have validation for all the information fields. Developers suggested to have validation only for necessary fields and to leave unnecessary fields out. What would be a testers contribution to this discussion?

We should not put too much validation, otherwise it may increase testing tasks

Validation is needed only for email address

Once the page is submitted, profile creation should not take more than 2 seconds

User story be estimable ,so that accurate estimation can be done for associated testing and development tasks

see justification of number 8 in sample exam

Explanation

see justification of number 8 in sample exam

10. Kanban is used to optimize the continuous flow of tasks by minimizing the (average) lead time for the complete value stream

True

False

Kanban is a project management methodology that aims to optimize the flow of tasks by reducing the average lead time for the entire value stream. By using visual cues and limiting work in progress, Kanban helps teams identify bottlenecks and improve efficiency. This allows for a smoother and faster workflow, ultimately reducing lead times and improving overall productivity. Therefore, the statement that Kanban is used to optimize the continuous flow of tasks by minimizing the average lead time for the complete value stream is true.

Explanation

Kanban is a project management methodology that aims to optimize the flow of tasks by reducing the average lead time for the entire value stream. By using visual cues and limiting work in progress, Kanban helps teams identify bottlenecks and improve efficiency. This allows for a smoother and faster workflow, ultimately reducing lead times and improving overall productivity. Therefore, the statement that Kanban is used to optimize the continuous flow of tasks by minimizing the average lead time for the complete value stream is true.

11. Match the content of agile manifesto with their counter parts.

Individual and interaction over

Working software over

Customer collaboration over

Responing to change over

Objective 1.1.1 : Recall the basic concept of Agile software development based on the Agile Manifesto

Explanation

Objective 1.1.1 : Recall the basic concept of Agile software development based on the Agile Manifesto

Submit

12. Agile Manifesto has the following statement of values:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

Which of the following is true about Agile Manifesto ?

Choices on the right have more value than choices on the left

Choices on both sides have equal value

Choices on the left has more value than choices on the right

Choices on the left and right have mixed values.

choices on the left has more values in Agile projects.

Explanation

choices on the left has more values in Agile projects.

13. An Agile team has been selected for a new project. The team consists of 9 people including developers, testers and business representatives. All the team members share the same work-space and participate in daily stand-up meeting. The team wants to implement whole team approach in their daily practices. What can be done to get the most benefit according to whole-team approach concept ? i. Making quality everyone's responsibility. ii. Make the team bigger by bringing in more testers and developers. iii. Reduce business representatives as they do not produce code or test feature. iv. Leverage the skills of every team mate, enabling various skill sets in the team. v. Making collaboration exclusive only between developers and business representative. vi. Enhance communication and collaboration within the team.

I only

I, ii, iii

I, iv and vi

Iv and vi only

Iv, v, and vi

To get the most benefit according to the whole-team approach concept, the team should focus on making quality everyone's responsibility (i) to ensure that all team members are accountable for delivering a high-quality product. Additionally, they should leverage the skills of every team mate (iv) by utilizing the diverse skill sets within the team, allowing for more efficient and effective problem-solving. Lastly, enhancing communication and collaboration within the team (vi) is crucial to ensure that everyone is aligned and working towards the same goals.

Explanation

To get the most benefit according to the whole-team approach concept, the team should focus on making quality everyone's responsibility (i) to ensure that all team members are accountable for delivering a high-quality product. Additionally, they should leverage the skills of every team mate (iv) by utilizing the diverse skill sets within the team, allowing for more efficient and effective problem-solving. Lastly, enhancing communication and collaboration within the team (vi) is crucial to ensure that everyone is aligned and working towards the same goals.

14. The concept of involving testers, developers and business representatives in all feature discussion is known as the power of _____

The concept of involving testers, developers, and business representatives in all feature discussions is known as the power of three. This approach recognizes the importance of collaboration and communication between these three key stakeholders in order to ensure that all perspectives and requirements are considered during the development process. By involving all three parties, the team can make more informed decisions, identify potential issues early on, and ultimately deliver a higher quality product that meets the needs of both the business and the end users.

Explanation

The concept of involving testers, developers, and business representatives in all feature discussions is known as the power of three. This approach recognizes the importance of collaboration and communication between these three key stakeholders in order to ensure that all perspectives and requirements are considered during the development process. By involving all three parties, the team can make more informed decisions, identify potential issues early on, and ultimately deliver a higher quality product that meets the needs of both the business and the end users.

Submit

15. After starting to continuous integration, team members in an agile project are more confident about their product and have constant visibility of their progress towards completion. How continuous integration helps to gain such benefit?

Continuous integration uses tools to autoamted most of the tasks

Code is compiled,built,deployed and tested on a daily basis and each days work begins with a stable system

Only testers with strong technical background are used in continuous integration.

None of the above

Continuous integration helps to gain the benefit of increased confidence and constant visibility of progress towards completion by ensuring that code is compiled, built, deployed, and tested on a daily basis. This means that any issues or bugs can be identified and addressed quickly, leading to a more stable system. By starting each day with a stable system, team members can be more confident in the quality of their product and have a clear understanding of their progress. The use of automated tools in continuous integration streamlines these processes and helps to ensure consistency and efficiency.

Explanation

Continuous integration helps to gain the benefit of increased confidence and constant visibility of progress towards completion by ensuring that code is compiled, built, deployed, and tested on a daily basis. This means that any issues or bugs can be identified and addressed quickly, leading to a more stable system. By starting each day with a stable system, team members can be more confident in the quality of their product and have a clear understanding of their progress. The use of automated tools in continuous integration streamlines these processes and helps to ensure consistency and efficiency.

16. Scrum does not provide guidelines on how to do testing.

True

False

Scrum, an agile framework for managing projects, does not provide specific guidelines on how to conduct testing. While Scrum emphasizes the importance of testing throughout the development process, it does not prescribe any specific testing methodologies or techniques. Instead, Scrum encourages teams to determine the most effective testing practices based on their specific project requirements and context. This allows teams to adapt and tailor their testing approaches to best suit their needs, promoting flexibility and continuous improvement.

Explanation

Scrum, an agile framework for managing projects, does not provide specific guidelines on how to conduct testing. While Scrum emphasizes the importance of testing throughout the development process, it does not prescribe any specific testing methodologies or techniques. Instead, Scrum encourages teams to determine the most effective testing practices based on their specific project requirements and context. This allows teams to adapt and tailor their testing approaches to best suit their needs, promoting flexibility and continuous improvement.

17. Communication,simplicity,feedback,courage and respect - what do these terms correspond to ?

5 values that XP embraces to guide development

XP principle

Scrum Best practices

Kanban guideline to software development

The given terms correspond to the 5 values that XP (Extreme Programming) embraces to guide development. XP is a software development methodology that emphasizes communication, simplicity, feedback, courage, and respect. These values are essential for effective collaboration and successful development in XP.

Explanation

The given terms correspond to the 5 values that XP (Extreme Programming) embraces to guide development. XP is a software development methodology that emphasizes communication, simplicity, feedback, courage, and respect. These values are essential for effective collaboration and successful development in XP.

18. Risk analysis is done only during release planning, not during iteration planning.

True

False

Risk analysis is not only done during release planning but also during iteration planning. Risk analysis is an important part of the Agile development process and is conducted at various stages to identify potential risks and mitigate them effectively. It helps in identifying and addressing risks related to scope, schedule, resources, and technology. By analyzing risks during both release planning and iteration planning, the team can proactively address any potential issues and ensure successful project delivery.

Explanation

Risk analysis is not only done during release planning but also during iteration planning. Risk analysis is an important part of the Agile development process and is conducted at various stages to identify potential risks and mitigate them effectively. It helps in identifying and addressing risks related to scope, schedule, resources, and technology. By analyzing risks during both release planning and iteration planning, the team can proactively address any potential issues and ensure successful project delivery.

19. Match the automated activities in continuous integration approach.

Reporting

Static Analysis

Integration

Compile

Unit testing

Submit

20. Which of the following are reasons for specification problem for software ? i. user's lack of insights into their true needs ii. absence for global vision for the system. iii. redundant or contradictory feature iv. miscommunication.

I,ii,iv

Ii,iii,iv

I,ii,iii

I,ii,iii,iv

The specification problem for software can be caused by various reasons. One reason is the user's lack of insights into their true needs, which means they may not fully understand or be able to articulate what they actually require from the software. Another reason is the absence of a global vision for the system, where there is a lack of overall understanding and planning for how the software should function within the larger context. Additionally, redundant or contradictory features can contribute to the specification problem, as they can lead to confusion and inconsistencies in the software requirements. Lastly, miscommunication between stakeholders can also be a factor, where misunderstandings or unclear communication can lead to incorrect or incomplete specifications.

Explanation

The specification problem for software can be caused by various reasons. One reason is the user's lack of insights into their true needs, which means they may not fully understand or be able to articulate what they actually require from the software. Another reason is the absence of a global vision for the system, where there is a lack of overall understanding and planning for how the software should function within the larger context. Additionally, redundant or contradictory features can contribute to the specification problem, as they can lead to confusion and inconsistencies in the software requirements. Lastly, miscommunication between stakeholders can also be a factor, where misunderstandings or unclear communication can lead to incorrect or incomplete specifications.

21. Which of the following is true about XP, Scrum and Kanban ? i. Scrum dictates specific software development technique (e.g. test first development) ii. Scrum and Kanban both use the visualization of workflow through task/white board or Kanban board iii. Iteration is essential in Scrum while it is not so for Kanban iv. Scrum visualizes and optimize the flow of work within a value-added chain.

I,iii and iv

Ii and iii

I, ii and iv

Ii only

See objective 1.2.1

Explanation

See objective 1.2.1

22. Which of the following are NOT true about release and iteration planning? i. Planning is an ongoing activity. ii. first iteration planning can start even after completing a number of iteration at the beginning of the project. iii. Release planning provide the basis for test approach and test planning. iv. Business representative establish and prioritize user stories for the release, in collaboration with the team

Ii

I,ii,iv

I,iii,iv

I,iv

not-available-via-ai

Explanation

not-available-via-ai

23. Retrospective can be used to assess productivity of testers, hence conducting audit to make the team more efficient.

True

False

Retrospective must be conducted in a professional environment with characterized by mutual trust.

Explanation

Retrospective must be conducted in a professional environment with characterized by mutual trust.

24. Here is a sample user story: User must be logged into the system to make a purchase. Once the purchase is done, system should send an email to user's email address. The whole purchasing act must be verified by a commercial security software. Users cannot purchase any negative number of item. What is missing from the above sample story? i. non-functional requirements ii. functional requirements.

I only

Ii only

Ii and ii

None

The missing aspect from the sample user story is non-functional requirements. Non-functional requirements define the qualities or characteristics of the system, such as performance, security, usability, and reliability, rather than specific functionalities. In this case, the non-functional requirements could include the need for the system to have a secure login process, the ability to handle a large number of users, and the requirement for the commercial security software to meet certain industry standards.

Explanation

The missing aspect from the sample user story is non-functional requirements. Non-functional requirements define the qualities or characteristics of the system, such as performance, security, usability, and reliability, rather than specific functionalities. In this case, the non-functional requirements could include the need for the system to have a secure login process, the ability to handle a large number of users, and the requirement for the commercial security software to meet certain industry standards.

25. Which of the following statements are true about the core principles of Agile Manifesto? i. Welcome changing requirements, even late in the development. ii. Conduct audit regularly to measure effectiveness of testers. iii. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. iv. It's okay to deliver products with minor bugs and unstable functionality.

I only

I and iii

Ii and iii

Iii only

Ii and iii

The core principles of Agile Manifesto promote the idea of welcoming changing requirements, even late in the development process. This allows for flexibility and adaptability in response to evolving needs. Additionally, the manifesto emphasizes the importance of maintaining a constant pace indefinitely, involving the sponsors, developers, and users. This ensures a sustainable and efficient workflow. The statement about conducting regular audits to measure the effectiveness of testers and delivering products with minor bugs and unstable functionality is not mentioned in the Agile Manifesto and therefore is not true.

Explanation

The core principles of Agile Manifesto promote the idea of welcoming changing requirements, even late in the development process. This allows for flexibility and adaptability in response to evolving needs. Additionally, the manifesto emphasizes the importance of maintaining a constant pace indefinitely, involving the sponsors, developers, and users. This ensures a sustainable and efficient workflow. The statement about conducting regular audits to measure the effectiveness of testers and delivering products with minor bugs and unstable functionality is not mentioned in the Agile Manifesto and therefore is not true.

26. Customer wants to innovate a new technology in a business domain which is not clear. They do not have a concrete idea about their requirements and thus are unable to provide a concrete functionality. The agile team developing the system decided to start the project anyway and clarify customer requirements as they move along. As the total amount of work is unknown, the agile team would like to have information regarding their productivity and ability to deliver, so that they can make accurate estimate as the project progresses. Which fundamental agile concept the software development team is applying?

Continuous integration

Working software

Early and frequent feedback

Planning

Retrospective

Early and frequent feedback avoid requirements misunderstanding and clarify customer feature request

Explanation

Early and frequent feedback avoid requirements misunderstanding and clarify customer feature request

27. The following describes a user story in a card: " Customers put their credit card information on the purchase form. The credit card number will be masked with asterisks except for the last 4 digits. For instance, if the the credit number is 334 567 5456, the text box would read *** *** 5456. The team needs 2-3 weeks to develop and test." 2-3 weeks to develop and tests. " According to 3C concept, which part of card is missing from the details?

Requirements

Criticality

Test and development duration

Acceptance criteria

The missing part from the details is the criticality. The question mentions the user story and the estimated time for development and testing, but it does not provide any information about the criticality of the user story. Criticality refers to the importance or priority of a user story, which helps the team in determining the order in which the user stories should be developed and tested.

Explanation

The missing part from the details is the criticality. The question mentions the user story and the estimated time for development and testing, but it does not provide any information about the criticality of the user story. Criticality refers to the importance or priority of a user story, which helps the team in determining the order in which the user stories should be developed and tested.

28. According to scrum, match the following concepts along with their terminology.

Backlog refinement

Sprints

Product increment

Product backlog

Sprint backlog

See the 7 instruments of scrum in syllabus

Explanation

See the 7 instruments of scrum in syllabus

Submit

29. Which of the following is a good reason that working software is more valuable than comprehensive documentation

Working software, albeit with reduced functionality, provides an opportunity to get rapid feedback

It helps the customer to understand their requirements better and gain global vision and insight to the software.

It helps to innovate in new problem domain where the requirements are not clear.

All of the above

None of the above

See object 1.1.1

Explanation

See object 1.1.1

30. Here is a sample user story: " when I am logged in to the system, it should be user friendly" Which of the part of INVEST technique is missing from the above statement ? i. Independent ii. Negotiable iii. Valuable iv. Estimable v. Small vi. Testable

Ii,iv,vi

I,v,vi

Ii,iv,v

Ii

The given correct answer, ii, iv, vi, suggests that the missing parts of the INVEST technique in the user story are negotiable, estimable, and testable. This means that the user story does not clearly define the aspects of the feature that are open to negotiation or discussion, does not provide a clear estimation of effort or resources required, and does not specify how the user-friendliness can be tested or verified.

Explanation

The given correct answer, ii, iv, vi, suggests that the missing parts of the INVEST technique in the user story are negotiable, estimable, and testable. This means that the user story does not clearly define the aspects of the feature that are open to negotiation or discussion, does not provide a clear estimation of effort or resources required, and does not specify how the user-friendliness can be tested or verified.

31. Which of the following is NOT true about scrum and Kanban ? i. Scrum does not dictate any software development techniques (e.g. test first development) ii. Both Scrum and Kanban use visualization of active tasks. iii. All the tasks in product backlog are put on the Kanban board and are moved across the board based on their progress. iv. Kanban board and each of its station can have pre-defined number of task in parallel.

I,ii,iii

Iii only

Ii,iii,iv

Iii and iv

Tasks are put on the Kanban board as soon as new space is available. Tasks move from product backlog to Kanban board to see its completion. Not the whole product backlog is put on the board.

Explanation

Tasks are put on the Kanban board as soon as new space is available. Tasks move from product backlog to Kanban board to see its completion. Not the whole product backlog is put on the board.

32. Here is a sample user story: "When I am logged in to check my emails, I want to identify all my new email instantly" What extra information below DO NOT make above user story estimable and/or testable according to INVEST technique ? i. All new email should be bold faced. ii. New email should be at the top of the pile. iii. the font of the email header should look nice. iv. It should not take more than 3 seconds to load the email.

Iii

I and ii

I,ii,iii

Iii and iv

i and ii are testable and iv is testable non-functional requirements of the story.
iii is not testable

Explanation

i and ii are testable and iv is testable non-functional requirements of the story.
iii is not testable

33. Which of the following are parts of benefit gained from continuous integration? i. Helps to build large complex systems through good test coverage, which can be obtained by Good automation tests covering as much functionality as possible. ii. Continuous integration helps to detect integration problem early as tests are run as part of continuous integration framework daily. iii. static code analysis, measure and profiling performance and extracting documentation can be done through use of build tools. iv. User stories are verified and broken down into smaller stories for understanding requirements better.

I,ii,iii,iv

I,ii,iii

I,ii,iv

Ii,ii,iv

Continuous integration is a software development practice that involves regularly merging code changes into a central repository and running automated tests to detect integration problems early. This helps to build large complex systems through good test coverage and automation tests. Additionally, continuous integration allows for static code analysis, measuring and profiling performance, and extracting documentation using build tools. Therefore, options i, ii, and iii are all parts of the benefits gained from continuous integration. Option iv, on the other hand, is unrelated to continuous integration.

Explanation

Continuous integration is a software development practice that involves regularly merging code changes into a central repository and running automated tests to detect integration problems early. This helps to build large complex systems through good test coverage and automation tests. Additionally, continuous integration allows for static code analysis, measuring and profiling performance, and extracting documentation using build tools. Therefore, options i, ii, and iii are all parts of the benefits gained from continuous integration. Option iv, on the other hand, is unrelated to continuous integration.

34. Which of the following is NOT a part of twelve principles of Agile Manifesto? i. Simplicity - the art of maximizing the amount of work not done - is essential. ii. the most efficient and effective method of communication is through face-to-face conversation. iii. Making quality everyone's responsibility. iv. Trust motivated individuals and give them the support and environment; build projects around them. v. Promote consistent project momentum

Iii and v

I, ii and iii

I, iv and v

Iii,iv, and v

Making quality everyone's responsibility is a benefit of whole team approach
Promoting consistent project momentum is an advantage of Early and frequent feedback

Explanation

Making quality everyone's responsibility is a benefit of whole team approach
Promoting consistent project momentum is an advantage of Early and frequent feedback

35. Which of the following is NOT an advantage of early and frequent feedback i. Enhance design and technical excellence ii. enable various use of skills among the team members and leverage upon it. iii. Avoid requirements misunderstanding, which may not have been detected until later in the development. iv. Provide information to the Agile team regarding its productivity and ability to deliver. v. Promoting consistent project momentum

V only

I and ii

I, ii and iv

Iii, iv, and v.

The correct answer is i and ii. This means that advantages of early and frequent feedback do not include enhancing design and technical excellence, as well as enabling various use of skills among the team members and leveraging upon it. The other options listed, iii, iv, and v, are all advantages of early and frequent feedback.

Explanation

The correct answer is i and ii. This means that advantages of early and frequent feedback do not include enhancing design and technical excellence, as well as enabling various use of skills among the team members and leveraging upon it. The other options listed, iii, iv, and v, are all advantages of early and frequent feedback.

36. Which of the following can be a challenge for implementing continuous integration. i. Team members often appreciate the use of unit tests rather than other tests. ii. Very few members of the team are technically strong in test automation or in continuous integration framework. iii. Continuous integration can be ineffective in case of inadequate test coverage. iv. Continuous integration can only be used with certain type of projects

I,ii,iii,iv

I,ii,iii

Ii,iii,iv

I,iv

Implementing continuous integration can be challenging due to several reasons. One challenge is that team members may prefer unit tests over other types of tests, which can create resistance towards adopting continuous integration practices that require a broader range of tests. Another challenge is that only a few team members may have the technical skills required for test automation and working with continuous integration frameworks. Additionally, inadequate test coverage can render continuous integration ineffective as it relies on comprehensive testing. Therefore, options i, ii, and iii are all valid challenges for implementing continuous integration. Option iv is not a challenge for implementing continuous integration, as it can be used with different types of projects.

Explanation

Implementing continuous integration can be challenging due to several reasons. One challenge is that team members may prefer unit tests over other types of tests, which can create resistance towards adopting continuous integration practices that require a broader range of tests. Another challenge is that only a few team members may have the technical skills required for test automation and working with continuous integration frameworks. Additionally, inadequate test coverage can render continuous integration ineffective as it relies on comprehensive testing. Therefore, options i, ii, and iii are all valid challenges for implementing continuous integration. Option iv is not a challenge for implementing continuous integration, as it can be used with different types of projects.

37. Which Two of the following can be topics in a retrospective meeting? i. We should have had more people in development team to get the iteration done shortly. ii. Testers and Developers should be conducting more social interaction to improve relationship. iii. The developed product is not user friendly. iv. The software market is getting is competitive

I,ii,iv

I and ii

Ii and ivii and iv

Iii and iv

Retrospective covers topic such as people,process,relationship, organization and tool
Objective: 1.2.3

Explanation

Retrospective covers topic such as people,process,relationship, organization and tool
Objective: 1.2.3

38. A Particular user story that was considered very simple turned out to be more complex, requiring more effort to implement and test. Which planning will get affected by this ?

Iteration planning

Release Planning

Both

None

The given scenario states that a user story that was initially perceived as simple turned out to be more complex, requiring additional effort for implementation and testing. This situation directly affects the iteration planning. Iteration planning involves breaking down user stories into smaller tasks and estimating the effort required to complete them within a specific iteration. If a user story turns out to be more complex than expected, it will impact the overall planning and scheduling of tasks within the iteration.

Explanation

The given scenario states that a user story that was initially perceived as simple turned out to be more complex, requiring additional effort for implementation and testing. This situation directly affects the iteration planning. Iteration planning involves breaking down user stories into smaller tasks and estimating the effort required to complete them within a specific iteration. If a user story turns out to be more complex than expected, it will impact the overall planning and scheduling of tasks within the iteration.

39. During a retrospective, developers decided on a coding and commenting style for their code to read and understand code better. What could be testers' contribution for test related improvement decisions? i. We should be doing more static analysis and code review, alongside automation testing ii. More and more integration tests should be automated to reduce regression risk. iii. Test cases must clearly state requirements rather than using vague assumption/expectation. iv. Our test strategy and consequently the developed test cases must satisfy acceptance criteria.

I,iii,iv

Ii,iii,iv

I,iv

I,ii,iii,iv

Retrospective can result in test related improvement decision based on test effectiveness, test productivity,test case quality and test satisfaction.

Explanation

Retrospective can result in test related improvement decision based on test effectiveness, test productivity,test case quality and test satisfaction.

40. Which of the following are testers' role during release planning? i. Defining testable user stories, including acceptance criteria ii. Breakdown user stories into tasks (particularly testing tasks) iii. Defining the necessary test levels. iv. Identify functional and non-functional characteristics of the system to be tested. v. Create acceptance criteria for the stories.

I,ii,iv

I,ii,iii

I,ii,iv

I,iii

During release planning, testers have the role of defining testable user stories, including acceptance criteria (i), and defining the necessary test levels (iii). These tasks involve ensuring that the user stories are clear and measurable, with specific acceptance criteria that can be used to determine if the story has been successfully implemented. Testers also play a crucial role in determining the appropriate test levels for the release, considering factors such as the complexity and criticality of the system. Therefore, the correct answer is i, iii.

Explanation

During release planning, testers have the role of defining testable user stories, including acceptance criteria (i), and defining the necessary test levels (iii). These tasks involve ensuring that the user stories are clear and measurable, with specific acceptance criteria that can be used to determine if the story has been successfully implemented. Testers also play a crucial role in determining the appropriate test levels for the release, considering factors such as the complexity and criticality of the system. Therefore, the correct answer is i, iii.

41. Which of the following are testers role during iteration planning? i. Participate in project and quality risk analysis ii. Estimate testing effort for all the testing tasks. iii. Support in creating automation tests for all test levels iv. Planning the testing v. Estimating testing effort associated with user stories.

Ii,iv,iv

I,iv

I,v

Iii,iv

Ii,iii

During iteration planning, testers have the role of estimating the testing effort for all the testing tasks (ii) and supporting in creating automation tests for all test levels (iii). This means they are responsible for determining how much time and effort will be required for testing and also for developing automated tests to streamline the testing process.

Explanation

During iteration planning, testers have the role of estimating the testing effort for all the testing tasks (ii) and supporting in creating automation tests for all test levels (iii). This means they are responsible for determining how much time and effort will be required for testing and also for developing automated tests to streamline the testing process.