New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ASTQB Exam ASTQB Topic 5 Question 83 Discussion

Actual exam question for ASTQB's ASTQB exam
Question #: 83
Topic #: 5
[All ASTQB Questions]

Your organization has just hired a test automation architect who has previously worked on medical software with strict regulatory requirements. His test automation framework is very solid and will allow the staff to build maintainable data-driven test cases. His tool choice is the top of the line tool that has been used for many years for traditional test automation. You are concerned that this is a very expensive tool and may not have the flexibility needed in your environment, particularly since the mobile applications your company develops are intended to exist in the market for only six months before being re-worked to add new features and change the user interface. The software development life cycle is iterative and the team uses continuous integration to provide testable software faster.

Given this information, what should you recommended for the test approach?

Show Suggested Answer Hide Answer
Suggested Answer: A

A is correct. It is important to use tools that are well suited for mobile. Keyword-driven test automation is likely to be more maintainable than data-driven, particularly when the application changes frequently. B is incorrect because high re-usability is not a goal for this project. High levels of coverage are probably not important in the test automation because the product has a short lifespan. Also, the tools may not be well-suited to mobile products. C is not correct because bypassing test automation violates the rules of the iterative lifecycles and would miss the opportunity of automating testing after the continuous integration occurs. D is not correct because the test automation should be used for the functional testing and needs to be done early in the lifecycle to ensure good product development and continuous integration testing.


Contribute your Thoughts:

Tamesha
4 days ago
Haha, manual functional testing? What is this, the 90s? If the app is changing that quickly, we'll need test automation to keep up. Might as well automate everything and save our sanity.
upvoted 0 times
...
Jesusita
12 days ago
Crowd-sourcing? Really? That's a recipe for chaos. Test automation is the way to go, even if the product has a short lifespan. Maintainability is still important.
upvoted 0 times
...
Rossana
15 days ago
I believe we should use test automation for performance testing and conduct functional testing manually.
upvoted 0 times
...
Benedict
17 days ago
I disagree, we should go with the proven framework for high coverage in test automation.
upvoted 0 times
...
Wava
18 days ago
I think we should search for other tools that are more suited for the mobile environment.
upvoted 0 times
...
Alexis
1 months ago
The proven framework is a good starting point, but I'm concerned about the lack of flexibility for the mobile apps. We'll need to find a balance between coverage and agility.
upvoted 0 times
...
Alyce
1 months ago
For a product with such a short life cycle, I think a keyword-driven approach would be more flexible and cost-effective than the expensive tool. Continuous integration will be key to staying on top of changes.
upvoted 0 times
...

Save Cancel