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

35 Questions | Total Attempts: 2181

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

Chapter 2


Questions and Answers
  • 1. 
    Which of the following is true about the difference between traditional and agile approach to software development?   i. There is considerable overlap and parallelism in agile as oppose to that in traditional approach. ii. In an 8 iteration release for an agile project, testing is done during or at the end of 7th and 8th release iii. System testing can come before integration testing in agile development iv. Only after half of iterations can the development team deliver value by releasing the software.  
    • A. 

      Ii and iv

    • B. 

      I and iii

    • C. 

      I and iii

    • D. 

      Iii and iv

  • 2. 
    What is common between agile and traditional software development approach ?
    • A. 

      In both cases, developers develop unit tests all the time.

    • B. 

      User stories are used to develop acceptance criteria in order to verify test result.

    • C. 

      Testers share their knowledge and testing skills with other team members

    • D. 

      Automation and use of tools are to key concept of both aproaches.

  • 3. 
    During an iteration, a change request from the customer created a number bugs due to regression. In addition to developing user stories selected for the iteration, now developers need to fix the regression issue and testers need to retest the feature. What could be done to mitigate the above issue?  
    • A. 

      Leave the bugs for later release and continue with the planned tasks for the release

    • B. 

      Stablize the iteration by taking the opportunity to 'fix bug first', test it and then integrate it, leaving the scheduled tasks until the end of iteration.

    • C. 

      Hide the bugs by changing the code, so that program execution will never go to the section of code which created the bug

    • D. 

      Wait for the customer to provide further report on the bug.

  • 4. 
    In an Agile project, the sequence of development activities has changed, along with the change in breath and depth of testing. Following the changes, the development team also changed their effort estimation for the iteration. What could trigger such situation in an iteration?
    • A. 

      Change of priority for user stories

    • B. 

      Some new members have joined the development team

    • C. 

      There has been a change in management.

    • D. 

      Developers and business representatives no longer appreciate the value of testing.

  • 5. 
    A development team, following an agile project, is distributed globally with team members living in different timezone. The team would like to apply pair programming for code review and testing design. How can they incorporate pair programming for their distributed team?  
    • A. 

      Bring team members periodically to share ideas and co-loate

    • B. 

      Make a new team who are geographically located nearby and let them handle the project

    • C. 

      Establish processes and tools to apply pair programming

    • D. 

      None of the above

  • 6. 
    Select the true statements regarding agile and traditional development. i. Most manual testing are done through exploratory or experience based testing in agile project. ii. Technical skills for testers are more important in traditional approach than in agile approach. iii. Tests are automated in all levels in agile development.  
    • A. 

      I only

    • B. 

      I and iii

    • C. 

      Ii and iii

    • D. 

      I,ii and iii

  • 7. 
    An Agile team would like to automate all their tests. They would also like to do exploratory or defect based testing,using fault-attack,error-guessing and other experience based approaches. Developers will develop unit cases, while testers will develop automated, system, integration and system integration tests. Which of the following choice would best benefit the agile team?  
    • A. 

      Train the developers to be testers and get testing done through them

    • B. 

      Higher highly skilled exploratory testers.

    • C. 

      Select testers wil strong automation and technical skills

    • D. 

      Use tools to automate testing, thus saving money by not hiring testers.

  • 8. 
    Agile developers often create automated unit tests
    • A. 

      True

    • B. 

      False

  • 9. 
    Which serves as a low level design specification?
    • A. 

      User stories

    • B. 

      Epics

    • C. 

      Test first approach test cases

    • D. 

      Entity diagrams

  • 10. 
    Which of the following activities could NOT occur in agile development? i. Lightweight documentation for testing , while heavy weight documentation for development. ii. break down user stories into smaller stories, and smaller stories to tasks. iii.always execute functional tests for current iterating, leaving previous tests not executed. iv. rigidly follow the principles of agile development with no adaptation or modification.
    • A. 

      I,iii,iv

    • B. 

      I,ii,iii

    • C. 

      Ii,iii,iv

    • D. 

      I,ii,iv

  • 11. 
    Which of the following is an example of integration between testing and development activity? i. A collection of user stories(e.g. epic) is describing tasks for all tiers in an N-tier architecture. ii. Test cases developed during test first approach are providing executable specification. iii. creating user documentation,which describes how to use the system. iv. Creating requirement specification,describing how the system will be built. v. lightweight documentation to trace errors and help with regression testing.
    • A. 

      I,ii,iii

    • B. 

      I,ii,v

    • C. 

      I,iii,iv

    • D. 

      Ii,iv,v

  • 12. 
    Which are the difference between agile and traditional in terms of test level? i. Both uses entry and exit criteria. ii. While traditional approach uses entry/exit criteria, agile approach does not. iii. considerable overlap of testing activity and test level in agile, as oppose to traditional. iv. Agile never accept changes after iteration planning is finished.
    • A. 

      I and iii

    • B. 

      Ii and iii

    • C. 

      I and ii

    • D. 

      Iii and iv

  • 13. 
    At the beginning of an iteration in an agile project, team needs to go through system testing due to some interface changes taken place recently. However, they are yet to go through unit testing and acceptance testing. How the team will handle this situation?
    • A. 

      They can perform system test because test level can overlap

    • B. 

      Perform unit tests, followed by the changes and leave system test at the end of iteration.

    • C. 

      Regression testing must come before unit and system testing.

    • D. 

      System testing can be performed anytime during an iteration

  • 14. 
    Although Scrum does not allow after the start of an iteration, some changes have been made to the items tested and developed in previous iteration. How the test team can reduce regression risk ?  
    • A. 

      Only perform confirmation test for the items changed.

    • B. 

      Perform all unit tests, functional test, and system test

    • C. 

      Perform functional test for items selected in this iteration and all previous iterations as part of regression suite.

    • D. 

      Since primary goal is to satisfy customer, perform all acceptance level testing(e.g. alpha and beta)

  • 15. 
    Consider the following user story: "When user clicks on the search button, it should take no longer than 3 seconds to post the search result on the page." When this user story can be tested ?
    • A. 

      Non-functional testing can be outsourced because it is specialized testing.

    • B. 

      Tests can be performed after two iterations after this iteration

    • C. 

      In a separate iteration dedicated for only non-functional testing

    • D. 

      As a part of system level testing after the completion of first user story.

  • 16. 
    As a part of continuous integration, the automated test suites comprises functional tests and unit tests. Moreover, when checking in code, stating analysis and code coverage needs to be done. Which of the following is the most efficient option to implement the above integration framework ?
    • A. 

      All the tests are executed with every code check in

    • B. 

      Static analysis , code coverage and unit tests during code check in and functional test at the end of iteration

    • C. 

      Static analysis, code coverage and unit test can be done during code check in while functional tests can be scheduled every couple of days.

    • D. 

      All tests are scheduled every couple of days.

  • 17. 
    There is a potential that code will break with every new change integrated with the software. In order to maintain a stable and working software, which one of the following do you need?
    • A. 

      Highly skilled developer who can solve software bugs most efficiently

    • B. 

      Real time test reporting to identify, isolate and correct bugs.

    • C. 

      Testers with development experience who can leverage on their debugging skill

    • D. 

      Complete integration framework with unit tests, static analysis, code checking and profiling happening during every code checking.

  • 18. 
    Which of the following can hamper test effectiveness ?
    • A. 

      Over reliance on unit testing

    • B. 

      Engage independent testers in the project

    • C. 

      Use tools to automate task boards and burndown charts

    • D. 

      Executing acceptance testing at least daily.

  • 19. 
    Which of the following can be an indicator of progress  for development and testing tasks.
    • A. 

      Burn down charts showing work left against time

    • B. 

      Task board showing the movement of different tasks across the board

    • C. 

      Customer survey with metrics such as, defect density, test pass/fail rate, defect discovery rate etc

    • D. 

      Daily stand up meeting with all the members attending the meeting.

  • 20. 
    Which of the following can provide an snapshot of current status of tasks selected for an iteration?
    • A. 

      Task boards with each type of tasks (dev,test) having color coordinated tasks

    • B. 

      Burndown charts showing work left to be finished against time allocated

    • C. 

      Daily stand up meeting

    • D. 

      Customer survey showing different metrics.

  • 21. 
    Testers would like to free their time and focus on designing and executing more test cases. Which of the followings can help to facilitate the above idea? i. Use wiki, wiki style dashboards to communicate project status. ii. Use tools to gather metrics to aid in process improvement and record test progress and test status data, thus sharing it through automated wiki or wiki style dashboard iii. Burn down charts iv. Task board
    • A. 

      I,iii

    • B. 

      I,ii

    • C. 

      Iii,iv

    • D. 

      I,iv

  • 22. 
    Which is NOT the purpose of communicating test status, progress and product quality.
    • A. 

      Making testers more effective and efficient through automated status sharing

    • B. 

      Measure product quality through customer survey, using various metrics

    • C. 

      Use metrics to reward, punish or isolate team members

    • D. 

      Make the progress towards the completion of iteration/releasevisible through burndown chart.

  • 23. 
    Change is inevitable in Agile project. During 6th iteration, customer requested to make changes to features developed and tested previously. Within the shorter time frame and and constant changes, which of the following would have an impact as testers need to review older test cases and corresponding software versions?
    • A. 

      Test design and implementation strategy

    • B. 

      Burn down charts

    • C. 

      Daily stand up meeting

    • D. 

      Early and frequent feedback to customer

  • 24. 
    Why testers need to review test cases regularly to add,modify,delete or categorize test cases? i. It is not possible to execute all the test cases, specially after a number of iterations ii. testers get good understanding on how the software has evolved through previous iterations. iii. due to excessive code churn,  test cases may become ineffective or fail. iv. to check if some other testers have made changes to working test cases.
    • A. 

      I and ii

    • B. 

      I and iii

    • C. 

      Ii and iii

    • D. 

      Iii and iv

  • 25. 
    Despite high code churn, what needs to be in place to maintain velocity without incurring large amount of technical debt? i. test automation at all level of testing ii. keep all the testing artifacts updated all the time. iii. enable version control through configuration management tool. iv. execute build verification testing
    • A. 

      I,ii,iii

    • B. 

      Ii,iii,iv

    • C. 

      I,iii,iv

    • D. 

      I,ii,iv

Back to Top Back to top