MENU
A new web site must operate correctly with different browsers (Internet Explorer, Google Chrome, Firefox, Netscape, Mozilla), using different plug-ins (Realplayer, Mediaplayer), will be receiving pages from different servers (IIS, Apache and WebLogic) and will be running on various server operation systems (windows 2007, XP, Linux)
Which of the following test techniques will you use to test this new web site in its various environments?
[K4] 3 credits
Suggested Answer: C
Get Premium ATA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
41 comments · newest first
SK
Skye
10 months ago
Wait, Netscape? Is that still a thing?
KA
Kanisha
11 months ago
Decision table testing seems too rigid for such a dynamic site.
RO
Roxane
11 months ago
Use case testing might not cover all scenarios here.
DE
Deonna
11 months ago
I think exploratory testing could uncover unexpected issues.
CA
Candida
11 months ago
Pairwise testing is a solid choice for this!
KA
Kassandra
12 months ago
Decision table testing sounds familiar, especially for handling different conditions, but I’m not clear on how it applies to multiple browsers and plug-ins.
TA
Tayna
12 months ago
I practiced use case testing before, and it seems like it might help with user interactions, but I’m not confident it addresses the technical environment variations.
RE
Ressie
12 months ago
I think exploratory testing could be a good option since it allows for flexibility, but I wonder if it covers all the necessary scenarios.
TE
Teri
1 year ago
I remember pairwise testing being useful for combinations, but I'm not sure if it's the best choice for all these different browsers and servers.
MA
Maile
1 year ago
Exploratory testing could be a good way to uncover any unexpected issues across these diverse environments. I'll make sure to thoroughly investigate the system and not just stick to a predefined set of test cases.
AR
Armanda
1 year ago
I'm a bit confused by all the different browsers, plug-ins, and server configurations. I'll need to make sure I understand them all before I can decide on the best testing approach.
KE
Keena
1 year ago
Hmm, this seems like a good opportunity to use pairwise testing. That should help me cover the key combinations without having to test every single possible scenario.
MA
Marguerita
1 year ago
This looks like a tricky one. I'll need to think carefully about the different variables involved and how to cover all the possible combinations.
AL
Alison
1 year ago
Hmm, I'm not totally sure about this one. The question mentions the file format is available for selection, so I'm wondering if the answer could be one of the other options like a Word doc or compressed file. I'll have to think this through carefully.
FR
Freeman
1 year ago
I think the sale of equipment would be reported as a capital gain, since equipment is considered a capital asset. The other options like inventory and government bonds don't seem to fit the criteria.
SA
Sanjuana
1 year ago
Exploratory testing, baby! It's like being a web detective, uncovering all the hidden bugs and quirks. Plus, I get to play around with the site, so it's basically getting paid to have fun. Can't beat that!
EA
Earleen
1 year ago
D) decision table testing
RI
Rikki
1 year ago
C) use case testing
TE
Teresita
1 year ago
B) exploratory testing
LA
Lauran
1 year ago
A) pairwise testing
VI
Viki
1 year ago
Pairwise testing, all the way! Gotta love how it covers all the bases without making me feel like I'm drowning in test cases. It's the Goldilocks of testing techniques, if you ask me.
RO
Ronny
1 year ago
Decision table testing might be helpful too, especially when dealing with different combinations of browsers, plug-ins, servers, and operating systems.
PA
Paulina
1 year ago
Exploratory testing could also be useful in this situation. It allows for flexibility and creativity in finding bugs.
DO
Dorthy
1 year ago
I agree, pairwise testing is definitely the way to go. It's efficient and covers a lot of different scenarios.
CO
Coral
1 year ago
Decision table testing? Really? That's a bit overkill for this, don't you think? I mean, how many possible combinations can there be?
GE
Gene
1 year ago
C) use case testing
LE
Lettie
1 year ago
B) exploratory testing
JE
Jenise
1 year ago
A) pairwise testing
CA
Casie
1 year ago
Use case testing is the way to do it, man. Got to make sure the site works end-to-end for all the different user scenarios. Can't leave anything to chance, you know?
SA
Sanjuana
1 year ago
C) use case testing
MA
Marci
1 year ago
B) exploratory testing
LE
Lezlie
1 year ago
A) pairwise testing
JI
Jimmie
1 year ago
I'm feeling exploratory on this one. With all those servers and OS variations, you never know what kind of funky behavior you might encounter. Gotta be ready to dive in and investigate!
DA
Daron
1 year ago
User4: Decision table testing might also be useful to ensure all scenarios are covered.
DI
Dierdre
1 year ago
User3: I prefer pairwise testing to cover all possible combinations.
SH
Shantell
1 year ago
User2: Agreed, with so many variables, we need to be ready to investigate.
ED
Edgar
1 year ago
User1: I think exploratory testing would be the way to go.
VE
Verona
1 year ago
Pairwise testing seems like the way to go here. Gotta cover all those browser and plugin combinations, you know? Keeps things efficient and comprehensive.
JE
Jeanice
1 year ago
I prefer exploratory testing, it allows for flexibility and adaptability in testing different environments.
SH
Shelia
1 year ago
I agree with Ezekiel, pairwise testing covers multiple combinations efficiently.
EZ
Ezekiel
2 years ago
I think pairwise testing would be the best option.