Online Test :: (Advanced ) Programming Test
Total Number of Questions56
Correct Answer0
Incorrect Answer0
Question Attempted0
Net Score0
System has been deployed.
As an additional technique after applying more formal techniques.
As a first approach of testing.
When testing with inexperience tester.
Is needed only until the software is released into production or use.
Does not need to be documented and commented, as it does not form part of the released software system.
Needs configuration management just like requirements, design and code?
Should be newly constructed for each new version of the software
100% condition coverage does not guarantee 100% decision coverage.
Error guessing has rules for testing.
Predicate Coverage uses Boolean values.
Condition coverage is also known as Predicate Coverage.
values as a program executes.The rate of change of data
The intrinsic complexity of the code.
The use of data on paths through the code.
Possible communications bottlenecks in a program.
All of these.
Stress testing.
Load testing.
Performance testing.
Defect Tracking.
Management reporting.
Deliverable base-lining.
Defect prevention.
Acceptance Testing.
Integration Testing.
Unit Testing.
Regression Testing.
Robustness.
Operability.
Observability.
Simplicity.
When database system is changed
When new functionality is introduced.
When system is installed on different hardware configuration than previously tested.
When project manager asks to perform.
Test environment details.
How to fix the fault.
Severity, priority.
How to reproduce the fault.
Verification.
Both Validation and Verification.
Neither Validation nor Verification.
Validation.
Although faults are most expensive to find during early development phases, they are cheapest to fix then.
They are easiest to find during system testing but the most expensive to fix then.
Faults are cheapest to find in the early development phases but the most expensive to fix then.
They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.
Equivalence partitioning.
Hybrid analysis.
Boundary value analysis.
Decision table.
None of the mentioned.
Measuring Response Time.
Measuring the LOC.
Measuring Transaction Rate.
No change.
Can’t say.
Increasing test time.
Reducing test time.
Project Plan.
Support Plan.
Business Plan.
Project Design.
Formal Follow up process.
No Pre Meeting Preparations.
Main Objective is to find defects.
Led by Trained Moderator (not the author).
Provide information for risk analysis and quality improvement.
Re-allocate resource to meet original plans.
Sign the system off for release.
Report on deviations from the project plan.
A process for selecting test cases.
A process for determining expected outputs.
A way to measure the quality of software.
A way to measure in a test plan what has to be done.
If you find a lot of bugs in testing, you should not be very confident about the quality of software.
The fewer bugs you find, the better your testing was.
The more tests you run, the more bugs you will find.
Component testing should be black box; system testing should be white box.
Measuring and analyzing results.
Evaluating exit criteria and reporting.
Preparing test specifications.
Determining the test approach.
Error Guessing.
Boundary Value Analysis.
Decision Table testing.
Test Analysis and Design.
Test Closure Activities.
Test Implementation and execution.
White Box Testing.
Open Box Testing.
Black Box Testing.
Grey Box Testing.
Gaining confidence in and providing information about level of quality.
Finding defects.
Preventing defects.
Fixing defects.
4
6
3
5
Process.
Flow.
Entity.
Level.
Inspection.
Walkthrough.
Both walkthrough and Inspection.
None of these.
To specify which modules to combine when and how many at once.
To ensure that all of the small modules are tested adequately.
To ensure that the system interfaces to other systems and networks.
To specify how the software should be divided into modules.
All the stakeholders.
QA Team.
Designer.
Tester.
Incremental model.
V-Model.
Spiral model.
Water fall model.
Check the technical accuracy of the document.
Find bugs in the program.
Ensure the ease of use of the document.
Ensure that the program is the latest version.
Evaluating exit criteria.
Test planning and control.
Test implementation and execution.
Test analysis and design.
The acceptance test does not necessarily include a regression test.
Verification activities should not involve testers (reviews, inspections etc.).
Test environments should be as similar to production environments as possible.
Performance testing can be done during unit testing as well as during the testing of whole system
Flexibility.
Maintainability.
Reusability.
Testability.
How well you know a particular technique
The objective of the test
How appropriate the technique is for testing the application
Whether there is a tool to support the technique
Performance Testing
Block box testing
Unit Testing
Regression testing
We cannot automate the user inputs
We cannot run the test
It may be difficult to determine if the test has passed or failed
It may be difficult to repeat the test
none of these
code coverage
fault injection
equivalence partitioning
Usability
Maintainability
Functionality
Supportability
Usability Testing
Security Testing
Boundary Value Analysis
Black box testing
White box testing
Dynamic testing
Static testing
Generating many transactions
Recovery testing
Measuring response time
Measuring transaction rates
Designer
Tester
QA Team
All the stakeholders
Go for retest and then use risk assessment to decide reasonable subset of regression test suit that will be executed.
Always go for full regression test
Just go for retest
Do not involve testers
Printing large document using printer in a queue.
All these
Generating a large amount of traffic on particular page.
Running multiple applications on a computer or server simultaneously.
User Requirements
Program Specification
Actual Results
System Specification
External and Internal resources respectively.
Internal resources only.
External resources only.
Internal and external resources respectively.
Unit testing
None of these
Integration testing
Validation testing
No, because they apply to development documentation
No, because they are normally applied before testing
Yes, because both help detect faults and improve quality
No, because they do not apply to the test documentation
Regressing testing
Adhoc testing
Recursive testing
Attend a tool exhibition
Analyze your needs and requirements
Find out what your budget would be for the tool
Invite a vendor to give a demo
Argue with development team and convince them to deliver build on time.
Ask for more resources.
Request customer about extending time.
Prioritize testing based on risk & make sure critical functionality is tested earlier.
Identifying test conditions and Identifying test cases
Identifying test conditions or Identifying test cases
Identifying test conditions only, not Identifying test cases
Not Identifying test conditions, Identifying test cases only
The system shall be user friendly.
The response time shall be less than one second for the specified design load.
The system shall be built to be portable.
The safety-critical parts of the system shall contain 0 faults.
