Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

iSQI Exam CTAL-TA_Syll2019 Topic 5 Question 40 Discussion

Actual exam question for iSQI's CTAL-TA_Syll2019 exam
Question #: 40
Topic #: 5
[All CTAL-TA_Syll2019 Questions]

You have been given a test charter to conduct exploratory testing for accepting credit and debit cards for an e-commerce system. You started with the credit cards and you have found that, valid or

invalid, they are never accepted. You have logged this as a defect. What should you do now?

Show Suggested Answer Hide Answer
Suggested Answer: D

The correct answer is D) Automate the testing for the credit card exploratory tests so they can be used for confirmation testing after the defect is fixed.

A) Enter your exploratory test cases with detailed test steps into the Test Management System

This is incorrect because entering the test cases into the Test Management System is not enough to document and track the exploratory testing process. The test cases should also include the expected results, actual results, and defects found during the testing. Moreover, the test cases should be organized into a clear and logical structure that reflects the test charter and scope.

B) Close the session and start a new session with a new charter

This is incorrect because closing and starting a new session with a new charter would mean losing all the information and data collected during the previous session. This would make it difficult to resume and continue the testing process from where it left off. Instead, it would be better to use a consistent and stable session with a single charter that covers all the requirements and features of the system.

C) Continue the session and conduct the testing for debit cards

This is incorrect because continuing the session and conducting only one type of card (debit) would not provide a comprehensive coverage of all possible scenarios and outcomes of accepting credit cards. It would also limit the scope of testing to only one aspect of payment processing, which may not reflect all the business rules, validations, exceptions, or integrations involved in this domain.

D) Automate the testing for the credit card exploratory tests so they can be used for confirmation testing after the defect is fixed

This is correct because automating some or all of the exploratory tests can help to save time, effort, and resources by reducing manual effort and increasing efficiency. It can also help to improve accuracy, consistency, and reliability by eliminating human errors and biases. Moreover, automating some or all of the exploratory tests can enable them to be reused for confirmation testing after fixing any defects found during exploratory testing. Confirmation testing is a type of functional testing that verifies that all requirements are met by performing regression tests on previously tested functionality1.


Contribute your Thoughts:

Filiberto
6 months ago
Option D sounds tempting, but then we'd have to actually, you know, do work. I'm more of a 'let's just wing it and see what happens' kind of tester.
upvoted 0 times
...
Darrin
6 months ago
I'm going with option C, 'cause I'm feeling lucky. Maybe we'll discover a secret credit card acceptance mode that only works on Tuesdays during a full moon.
upvoted 0 times
Gladis
5 months ago
Yeah, it's worth exploring further to ensure all payment methods are working correctly.
upvoted 0 times
...
Annice
6 months ago
Good idea, let's see if we can find any issues with debit card acceptance.
upvoted 0 times
...
Leila
6 months ago
I think we should go with option C and continue testing with debit cards.
upvoted 0 times
...
...
Karan
6 months ago
Automate the credit card tests? What is this, the 90s? Let's just keep exploring, I'm sure we'll find some juicy defects that will make the devs cry.
upvoted 0 times
...
Denna
6 months ago
Hmm, I'd say continue the session and test the debit cards. Maybe the credit card issue is just the tip of the iceberg, and we'll find a whole treasure trove of bugs to report.
upvoted 0 times
Nan
5 months ago
That's a good point. Let's see what other issues we can uncover with the debit cards.
upvoted 0 times
...
Alaine
6 months ago
C) Continue the session and conduct the testing for debit cards
upvoted 0 times
...
Dorcas
6 months ago
A) Enter your exploratory test cases with detailed test steps into the Test Management System
upvoted 0 times
...
...
Glen
6 months ago
If the credit cards are never accepted, why would we even bother with debit cards? Might as well just pack up and go home.
upvoted 0 times
Michael
5 months ago
C) Continue the session and conduct the testing for debit cards
upvoted 0 times
...
Kimbery
5 months ago
A) Enter your exploratory test cases with detailed test steps into the Test Management System
upvoted 0 times
...
Jose
5 months ago
If the credit cards are never accepted, we need to log the defect and continue testing with debit cards.
upvoted 0 times
...
Leonida
5 months ago
A) Enter your exploratory test cases with detailed test steps into the Test Management System
upvoted 0 times
...
Dahlia
6 months ago
If the credit cards are never accepted, we need to log the defect and continue testing with debit cards.
upvoted 0 times
...
Jame
6 months ago
A) Enter your exploratory test cases with detailed test steps into the Test Management System
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77