The software industry is at it's a more comfortable room, and why would it not be? After all, everything is now connected with softwares. Computers are operating almost every area of human lives, whether it's education, research, health care, military-defense, or hospitality, so on. Powerful softwares are being created to make lives easier, but there can happen anomalies. These anomalies or say bugs can ruin the whole functioning of softwares; that's why software testing exists. This is quite a long quiz but very interesting and important.
Specification-based.
Structure-based.
Experience-based.
Reference-based.
Rate this question:
Unit Testing.
Integration testing.
System testing.
Acceptance testing.
Rate this question:
Testing.
Dynamic testing.
Debugging.
Revers engineering.
Rate this question:
A testing technique used to guess where a developer is likely to have made a mistake.
A technique used for assessing defect metrics.
A development technique to verify that all error paths have been coded.
A planning technique used to anticipate likely schedule variances due to faults.
Rate this question:
Black-box.
White-box.
Specification-based.
Behavior-based.
Rate this question:
Regression testing.
Debugging.
Dynamic analysis.
Static analysis.
Rate this question:
Functional.
Non-functional.
Structural.
Change-related.
Rate this question:
Static testing is performed by developers; dynamic testing is performed by testers.
Manual test cases are used for dynamic testing; automated tests are used for static testing.
Static testing must be executed before dynamic testing.
Dynamic testing requires executing the software; the software is not executed during static testing.
Rate this question:
Planning.
Review initiation.
Individual review.
Fixing and reporting.
Rate this question:
Grey-Box.
Black-box.
White-box.
Exploratory.
Rate this question:
Configuration Management.
Debugging.
Test and defect management.
Risk analysis.
Rate this question:
Unit and integration.
Integration and system.
System and acceptance.
All levels.
Rate this question:
The project manager.
The test manager.
The tester.
The product owner.
Rate this question:
Escalate the issue to human resources and stress the importance of mutual respect.
Communicate in a setting with senior management to ensure everyone understands.
Convince the developer to accept the blame for the mistake.
Remind them of the common goal of creating quality systems.
Rate this question:
Helps to better identify and correct the root cause of defects.
Outlines how development teams can code faster.
Specifies the desired root causes to be achieved by other teams.
Contributes to the justification of future project funding.
Rate this question:
Dynamic testing is less reliable in finding bugs.
Pesticides mixed with static testing can allow bugs to escape detection.
Tests should not be context dependent.
Running the same tests over and over will reduce the chance of finding new defects.
Rate this question:
Error guessing.
Automated regression testing.
Providing inputs and examining the resulting outputs.
Code review.
Rate this question:
A tester finds a defect and reports it.
A tester retests a fix from the developer and finds a regression.
A developer finds and fixes a defect.
A developer performs unit testing.
Rate this question:
Traceability between the test cases and the requirements.
Coverage of the risk items by test case.
Traceability between the requirements and the risk items.
Coverage of the requirements by the test cases that have been designed.
Rate this question:
The project manager.
The product owner.
The test manager.
The tester.
Rate this question:
70, 75
65, 72, 80
69, 70, 75, 76
70, 71, 74, 75, 76
Rate this question:
The test plan.
The test approach.
The test case template.
The project plan.
Rate this question:
To ensure the system still functions as expected with no introduced issues.
To ensure no unauthorized changes have been applied to the system.
To assess the scope of maintenance performed on the system.
To identify any maintainability issues with the code.
Rate this question:
Ad hoc.
Walk-through.
Inspection.
Audit.
Rate this question:
Roll out, adapt, train, implement.
Monitor, support, revise, implement.
Learn, evaluate, decide, assess.
Evaluate, adapt, monitor, support.
Rate this question:
You can find defects that might be missed by more formal techniques.
You can test for defects that only experienced users would encounter.
You can target the developer’s efforts to the areas that users will be more likely to use.
It is supported by strong tools and can be automated.
Rate this question:
Developers are not good testers.
Developers are not quality focused.
Developers are not objective about their own code.
Developers do not have time to test their own code.
Rate this question:
The root cause is the old equipment and the effect is the new equipment.
The root cause is the customer complaints and the effect is the social media postings.
The root cause is conducting the testing on the wrong version of the equipment and the effect is the customer complaints and postings.
The root cause is the software failing on the later model and the effect is the customer complaints.
Rate this question:
6
8
10
12
Rate this question:
Test monitoring.
Test planning.
Test closure.
Test control.
Rate this question:
1
2
5
Unknown with this information.
Rate this question:
Facilitator.
Author.
Scribe.
Manager.
Rate this question:
An informal development review.
A walk-through.
An inspection.
An audit.
Rate this question:
Error guessing.
Intuitive testing.
Oracle-based testing.
Exhaustive testing.
Rate this question:
A developer makes a mistake which causes a defect that may be seen as a failure during dynamic testing.
A developer makes an error which results in a failure that may be seen as a fault when the software is executed.
A developer has introduced a failure which results in a defect that may be seen as a mistake during dynamic testing.
A developer makes a mistake which causes a bug that may be seen as a defect when the software is executed.
Rate this question:
The speed of response from the banking back-end.
The attractiveness of the application.
The size and clarity of the instruction text.
The reliability of the application when the connection is dropped.
Rate this question:
Planning.
Implementation.
Execution.
Reporting.
Rate this question:
Unit and integration only.
System testing only.
Integration, system and acceptance only.
Unit, integration, system and acceptance only.
Rate this question:
It is a form of stress testing.
It is not feasible except in the case of trivial software.
It is commonly done with test automation.
It is normally the responsibility of the developer during unit testing.
Rate this question:
An error causes a failure which results in a defect.
A defect causes a failure which results in an error.
A failure is observed as an error and the root cause is the defect.
An error causes a defect which is observed as a failure.
Rate this question:
During the planning activities.
During the implementation and execution activities.
During the monitoring activities.
During all the activities.
Rate this question:
The developer won’t know how important the problem is.
The developer won’t know how to repeat the test.
The developer won’t be able to see what the tester is saying is wrong.
The developer won’t know what the tester expected to see.
Rate this question:
Defects can be identified that might not be caught by dynamic testing.
Early defect identification requires less documentation.
Early execution of the code provides a gauge of code quality.
Tools are not needed because reviews are used instead of executing code.
Rate this question:
A module that performs incorrect calculations due to a defect in a formula.
A failed performance test.
An issue with the interface between the system under test and a peripheral device.
A problem with the development manager which is resulting in his rejecting all defect reports.
Rate this question:
1
2
3
4
Rate this question:
It runs automated test scripts to test the test object.
It automatically records defects in the defect tracking system.
It analyzes code to determine if there are any coding standard violations.
It tracks test cases, defects and requirements traceability.
Rate this question:
The point during software development when testing should start.
The body of knowledge used for test analysis and design.
The source to determine the actual results from a set of tests.
The method used to systematically devise test conditions.
Rate this question:
Gaining confidence.
Finding defects.
Preventing defects.
Providing information for decision making.
Rate this question:
Quiz Review Timeline (Updated): Mar 22, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.