Free Certified Tester Advanced Level Agile Technical Tester Exam CTAL-ATT Exam Practice Test

Which of the following is a correct statement?

• Test automation is a procedure
• Test automation is a test objective
• Test automation is a strategy
• Test automation is a methodology

As a tester on an Agile team you have been given the following user story to analyzeAs a medical professionalI want to see the availability of operating roomsSo I can schedule surgeries as neededYou have talked with the product owner and she expressed some concern over the term 'medical professional' You have looked into this and found that doctors want to schedule their surgeries but the hospital administrator does not want them to have this ability At this point what should you do to try to resolve this issue?

• Wait for the team to sort out the requirements and test something else in the meantime
• Continue with testing from the perspective of a doctor and trust the procedures to be worked out later regarding who can do what
• Work with the BA and the product owner to try to negotiate the differing approaches and come to an agreement
• Expand the testing to cover all personas to ensure that everyone can use the application and let the process sort out later when access is allowed to the application

You are developing a test automation suite for an agile project and want to include as much coverage as possible Unfortunately one of the critical web services (e-commerce checkout) is not scheduled for completion until the later iterations Which of the following would be a good option to allow you to progress with your end-to-end test automation without creating too much extra work?

• Write the missing web service yourself and then hand over that code to the developers for further refinement
• Have the automation create a stub to replace the service for each execution and destroy the stub after execution is complete
• Use a service virtualization tool to create a virtualized service to be used by the test automation
• Use a service from a legacy product and integrate it with the system to allow use by the test automation

A developer has implemented a class that calculates if a given date is a leap year. The definitionfor the leap year is given:Every year that is exactly divisible by four is a leap year, except for years that are exactlydivisible by 100, but these centurial years are leap years if they are exactly divisible by 400.- divisible by 4- but not by 100- years divisible by 400 are leap anywayYou have already thought about it and started with the first test class; the test class looks like(pseudo JavaScript used here):// LeapYear.spec.jsdescribe('Leap year calculator', () => {it('should consider 1996 as leap', () => {expect(LeapYear.isLeap(1996)).toBe(true);});});What would now be your next step to proceed as efficient as possible, to validate the correctnessof the class above?

• First write additional test classes to test also other relevant aspects of the leap year calculation
• First write code that covers other relevant aspects of the leap year calculation
• First write code that makes this test case fail
• First write code that makes this test case pass

You are working for an organization that has implemented CI and is struggling to get the automated tests to run on each build because of time limitation. On average, there are three ad hoc builds per day one scheduled build overnight one scheduled build on Friday nights and one build that is conducted on the Thursday night before the end of the sprint on the second Friday. There are four sets of tests high priority medium priority low priority, nonfunctional. The non-functional tests must be run in the integrated stage environment whereas the other tests can be run in any of the test environmentsIn addition to just the execution time of the tests it has also been noted that reviewing the results of the tests take about two hours per set of testsGiven this information which of the following is the most efficient and effective approach to test automation execution?

• Run all four test sets every night
• Run all the high priority tests for every build low priority tests at night and the medium priority tests at the end of the sprint
• Run all four test sets on every build
• Run the high priority tests on each build the medium priority tests every night the low priority tests every week and the non-functional tests on the Thursday night before sprint end

You have been asked to supply the data file for a data-driven test automation script that will be used to test the following story:As a customer I want to be told how many items I need to purchase, so I can receive free shippingYou have been told the automation will verify whether or not the free shipping message is displayed. Which of the following columns should appear in your data file to support the automated testing of this story?

• customer name # items, price of items, total shipping cost
• item ID quantity purchased free shipping (y/n)
• quantity purchased, free shipping (y/n), total shipping cost
• item ID quantity purchased free shipping (y/n), item shipping cost total shipping cost

''As the leader of the marketing department, I want to have a content management system so thatmy employees can edit and provide quality content to the readers''Which of the following requirements engineering techniques would be the MOST effective foridentifying and prioritizing user stories for the given Epic?

• Storyboarding
• Story mapping
• Defining Personas
• Class Diagrams
• Use Cases

Summarize the characteristics of test automation in relation to development projects.

• Test automation can play an important role in test environment configuration and test release acquisition
• In large projects, there is usually one best solution that fits all needs, and so. on dedicated test automation strategies fits best
• Test automation supports the goals of an iteration directly, e.g., by reducing the regression risk associated with stability of the system
• Supportive test automation effort must be done in the teams of the iteration teams themselves

You are testing a large e-commerce system for household goods that is being implemented using Agile methodologies You are currently working on deriving tests tor stories that are implementing the following epic.As a customer I want to use the e-commerce system, so that I can have my purchased goods delivered to my house.The story you are currently working on isAs a customer I want to be told how many items I need to purchase, so I can receive free shippingWhich of the following is an appropriate test charter for this story?

• Login as a customer buy various goods request free delivery add more items to your cart checkout, verify that your delivery is free
• Buy 12 of one item and see if you are advised that you get free shipping
• Login as a customer buy an item verify message tells you how many are needed for free delivery add items to your cart until you qualify checkout verify delivery is free
• As a supplier verify that when a customer purchases the correct number of goods the system doesn't add any delivery fees at checkout

Your organization has been making animal food dispensers for free-range chickens and has been using a combination of test automation exploratory testing and some black-box testing on all products. The company has been using the following approach to the testing of the high-risk items:Exploratory testing = 85%Black-box testing = 15%Test automation = coverage goal is 25% but time is only allocated to automation if no other testing is needed, so the coverage is currently about 5% and the automation suite is run only infrequently.The company has decided to modify their product and use it for pill dispensing for pharmacies Regardless of the mechanical challenges of this modification you now have to determine how testing should be adjusted for this safety critical application Which of the following would follow the guidelines in the syllabus for the testing approach for the high-risk items?

• Exploratory testing = 85% Black-box testing = 15% Test automation = 25% coverage executed infrequently
• Exploratory testing = 15% Black box testing = 85% Test automation = 25%, executed for every code release
• Exploratory testing = 50% Black box testing = 50% Test automation = 50% coverage executed before every production release
• Exploratory testing = 25% Black-box testing = 75% Test automation = 75% coverage executed for every code release