Online Test :: (Beginner) Programming Test
Total Number of Questions54
Correct Answer0
Incorrect Answer0
Question Attempted0
Net Score0
Quality plans.
Test environments.
Test items (i.e. software versions).
What is not to be tested?
Pre-release testing by end user representatives at their sites.
The first testing that is performed.
Post-release testing by end user representatives at the developer’s site.
Pre-release testing by end user representatives at the developer’s site.
Both Process and Product.
Process.
Neither Process nor Product.
Product.
Agile model.
V-V model (V Model).
Waterfall model.
Rapid action development model.
Software Process.
Testing Process.
Delivery Process.
None of these.
As soon as testing begins.
After system testing is done.
When user asks.
When user requirements are gathered.
Functional and behavioral.
Algorithmic and data structure.
Architectural and structural.
Usability and reliability.
Test Requirement.
Test Specification.
Test Configuration.
Test Planning.
It depends on the risks for the system being tested.
Time has run out.
All the planned tests have been run.
All faults have been fixed correctly.
Equivalence class partitioning.
Boundary value testing.
Decision tables.
Boundary value testing AND Equivalence class partitioning.
Acceptance testing.
System testing.
Integration testing.
Component testing.
System has been deployed.
As an additional technique after applying more formal techniques.
As a first approach of testing.
When testing with inexperience tester.
Usability Assessment.
Installation Test.
Coverage Analysis.
Code Inspection.
Requirement.
Analysis.
Coding.
Test Plan.
Software Module development life cycle.
Bug life cycle.
Software development life cycle.
Software testing life cycle.
Plan, Do, Check, Act.
Plan, Do, Correct, Act.
Plan, Do, Check, Accept.
Plan, Debug, Check, Act.
A test case is a documentation which specifies input values, expected output and the preconditions for executing the test.
Find the defects in software products.
Minimize the maintenance and software support costs.
Avoid post deployment risks.
Includes Metrics.
Pre Meeting Preparations.
Formal Follow up Process.
Scenario, Dry Run, Peer Group.
None of the mentioned.
ALL of the mentioned.
Test case generation.
Test case design.
Test procedure.
Test suite.
Test data.
Test log.
Capable off the shelf software.
Commercial off the shelf software.
Change control of the software.
Compliance of the software.
Designer.
Customers.
Developer.
Business Analyst.
Structural testing.
Code-Based Testing.
All of these.
Clear box testing.
Support plan.
Business plan.
Project plan.
Alpha testing.
Field testing.
Performance testing.
Verified.
Critical.
Deferred.
Postponed.
Relinquishments of control.
Does not meet people needs.
Cultural difference.
Loss of control over reallocation of resources.
Validation.
Requirement engineering.
Verification.
Test plan.
Test design specification.
Test procedure specification.
Test case specification.
High Severity and High Priority.
High Severity and Low Priority.
Low Severity and High Priority.
Low Severity and Low Priority.
System Testing.
Unit Testing.
Big-Bang Testing.
Integration Testing.
Specification.
Code.
Design.
You shorten the time required for testing.
You do the best testing in the time available.
You find more faults.
You do more effective testing.
Spiral model.
V model.
Iterative model.
To find faults in the software.
To assess whether the software is ready for release.
To demonstrate that the software doesn’t work.
To prove that the software is correct.
lack of Testing Tools
lack of Objectives
lack of Technical Documents
lack of Training
Performance testing
Unit testing
Business scenarios
Static testing
Test high risk areas.
Obtain good test coverage.
find as many faults as possible
Test whatever is easiest to test.
Test configuration
Test recording
Test specification
Test planning
UAT
Unit Testing
Walk through
System testing
Behavioral Testing
none of the mentioned
Flow Testing
Data Testing
Users
All of the mentioned
Testers
Developers
Severity
Fix ability
Traceability
Priority
White box testing
Black box testing
Both White box testing and Black box testing
Grey box testing
The most difficult tests first(to allow maximum time for fixing)
The order they are thought of
The easiest tests first(to give initial confidence)
The most important tests first
Risks
Schedule
Incident reports
Features to be tested
Authors are not present during inspections, whilst they are during walkthroughs.
A walkthrough is lead by the author, whilst an inspection is lead by a trained moderator.
An inspection has a trained leader, whilst a walkthrough has no leader.
An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator.
Grey box Testing and White box Testing
Black box Testing
Grey box Testing
White box Testing
Security testing
Usability testing
Boundary value analysis
Both Developers place and User place
neither Developers place nor User place
User place
Developers place
Customer
Developer
Designer
Software tester
End Users
Testers & Developers
