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

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ASTQB Exam - 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.


by Dean at Nov 13, 2024, 04:43 PM

Limited Time Offer

25%

Off

Get Premium ASTQB Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Fabiola
3 months ago
Manual testing for a short life cycle could save time, I like option D.
upvoted 0 times
...
Marylou
3 months ago
Wait, crowd-sourcing? Isn’t that risky for quality?
upvoted 0 times
...
Delsie
3 months ago
But isn’t the proven framework worth the investment for coverage?
upvoted 0 times
...
Deandrea
4 months ago
Totally agree, the current tool seems too rigid for our needs.
upvoted 0 times
...
Jodi
4 months ago
I think we should look for tools that fit mobile better.
upvoted 0 times
...
Rasheeda
4 months ago
Performance testing automation sounds reasonable, but I'm worried about relying solely on manual testing for functionality. It might lead to missed bugs in such a fast-paced cycle.
upvoted 0 times
...
Pearly
4 months ago
I feel like we should definitely consider the mobile environment more. Keyword-driven tests might give us the flexibility we need, but I'm not entirely confident about that approach.
upvoted 0 times
...
Naomi
4 months ago
I remember a practice question where we had to decide between manual and automated testing for short-lived projects. I think crowd-sourcing could be a viable option here.
upvoted 0 times
...
Alaine
5 months ago
I'm not sure if going with the proven framework is the best choice since our apps change so quickly. Maybe we should look for something more flexible.
upvoted 0 times
...
Art
5 months ago
I like the idea of using test automation for performance testing and doing the functional testing manually. That could be a good compromise given the product's short lifespan. But I'd want to make sure the manual testing is still thorough and efficient.
upvoted 0 times
...
Talia
5 months ago
Crowd-sourcing for a product with such a short life cycle? That seems like a risky approach to me. I'd want to maintain some control over the testing process, even if it means investing in a more flexible automation solution.
upvoted 0 times
...
Lucy
5 months ago
Hmm, I'm a bit torn on this. The proven framework sounds appealing, but the lack of flexibility could be an issue. I think I'd lean towards exploring some more mobile-friendly tools, even if it means a bit more setup work upfront.
upvoted 0 times
...
Jennie
5 months ago
This is a tricky one. I'm not sure if the expensive tool is really worth it given the short product life cycle and need for flexibility. Maybe we should look into more agile test automation options.
upvoted 0 times
...
Tamesha
1 year 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
Laurene
1 year ago
A) 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
...
Tijuana
1 year ago
B) Go with the proven framework and seek high coverage in the test automation software to ensure good reuse.
upvoted 0 times
...
Quiana
1 year ago
A) Search for other tools that are more suited for the mobile environment and consider creating test automation with keyword-driven tests rather than data-driven.
upvoted 0 times
...
Noah
1 year ago
B) Go with the proven framework and seek high coverage in the test automation software to ensure good reuse.
upvoted 0 times
...
Jerry
1 year ago
A) Search for other tools that are more suited for the mobile environment and consider creating test automation with keyword-driven tests rather than data-driven.
upvoted 0 times
...
...
Jesusita
1 year 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
Ernest
1 year ago
B) Yes, we need to ensure that our test automation is maintainable and flexible, even with the short lifespan of our product.
upvoted 0 times
...
Jerilyn
1 year ago
A) I agree, finding a tool that is more suited for our mobile environment and using keyword-driven tests seems like a better approach.
upvoted 0 times
...
Keshia
1 year ago
B) Go with the proven framework and seek high coverage in the test automation software to ensure good reuse.
upvoted 0 times
...
Arthur
1 year ago
A) Search for other tools that are more suited for the mobile environment and consider creating test automation with keyword-driven tests rather than data-driven.
upvoted 0 times
...
...
Rossana
1 year ago
I believe we should use test automation for performance testing and conduct functional testing manually.
upvoted 0 times
...
Benedict
1 year ago
I disagree, we should go with the proven framework for high coverage in test automation.
upvoted 0 times
...
Wava
1 year ago
I think we should search for other tools that are more suited for the mobile environment.
upvoted 0 times
...
Alexis
1 year 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 year 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
Valentin
1 year ago
B) Continuous integration will definitely help us stay on top of changes and ensure efficient testing.
upvoted 0 times
...
Oliva
1 year ago
A) I agree, a keyword-driven approach would be more flexible and cost-effective for our short life cycle product.
upvoted 0 times
...
Julieta
1 year ago
B) Go with the proven framework and seek high coverage in the test automation software to ensure good reuse.
upvoted 0 times
...
Lashawnda
1 year ago
A) Search for other tools that are more suited for the mobile environment and consider creating test automation with keyword-driven tests rather than data-driven.
upvoted 0 times
...
...

Save Cancel