1. Which of the following statements is incorrect in relation to Code coverage?
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
Answers:
- It describes the degree to which the source code of a program has been tested
- It is a form of White-box testing
- It is a form of Black-box testing
Answers:
- people have difficulty in understanding the instructions
- people have difficulty in manipulating the parts
- people have difficulty in interpreting the feedback
- all of the above
Answers:
- A software testing design technique in which tests are designed to include representatives of boundary values
- A type of software testing used for testing two or more modules or functions together with the intent of finding interface defects between the modules or functions
- It is the degree to which the source code of a program has been tested
- A software testing technique that divides the input data of a software unit into partitions of data from which test cases can be derived
Answers:
- It tests values at and near the minimum and maximum allowed values for a particular input or output
- It tests different combinations of input circumstances
- It is a testing technique associated with White-box testing
- Both a and b
Answers:
- Performance errors
- Logical errors
- Typographical errors
- Behavioral errors
Answers:
- Single testing
- Pairwise testing
- Unit testing
- None of the above
Answers:
- Automating the testing process
- Executing test suites of test cases
- Generating test reports
- Creating reusable test logic to reduce maintenance and improve test coverage
Answers:
- Major decision points are tested in the early phase
- No drivers need to be written
- No stubs need to be written
- Regression testing is not required
Answers:
- Test Automation is the process of writing a computer program to do testing that would otherwise need to be done manually.
- Test Automation is the use of software to control the execution of tests and the comparison of actual outcomes to predicted outcomes.
- Test Automation tools may provide record and playback features that allow users to interactively record user actions and replay it back any number of times.
- Test Automation is the set of procedures used by organizations to ensure that a software product will meet its quality goals at the best value to the customer.
Answers:
- True
- False
Answers:
- Integration
- Performance
- Regression
- Stability
Answers:
- Code complexity analysis
- Profiling
- Network packet sniffing
- Spelling and grammar checking
- Program slicing
Answers:
- Static analysis tool
- Debugging tool
- Test management tool
- Configuration management tool
Answers:
- Code review
- Inspection
- Walkthroughs
- System tests
Answers:
- A Stub is basically the same as a driver except that it is very fast in returning results
- A Stub is a dummy procedure, module or unit that stands in for an unfinished portion of a system
- A Stub is just a different name for an Emulator
- None of the above
Answers:
- Disk space
- Network bandwidth
- Internal memory
- All of the above
Answers:
- Test Run
- Test Script
- Test Plan
- Test Scenario
Answers:
- Agile model
- Waterfall model
- V-Model
- Spiral model
Answers:
- Unit, Integration, System, Validation
- System, Integration, Unit, Validation
- Unit, Integration, Validation, System
- None of the above
Answers:
- Inspection
- Audit
- White-box testing
- Walkthrough
Answers:
- It is random testing performed by automated testing tools
- It is used to simulate the actions a user might perform
- It is another name for Monitor testing
Answers:
- Load/Stress testing
- Unit testing
- Security testing
- Stress testing
Answers:
- Fuzz testing
- Black-box testing
- Sanity testing
- Smoke testing
Answers:
- Regression testing
- Maintenance testing
- Confirmation testing
- None of the above
Answers:
- Improper handling of sequences of events
- Mis-handling of combinations of conditions
- Irregular handling of large and small values
- Improper handling of input classes
- Invalid output generation
Answers:
- Recovery testing and failover testing
- Performance, Load and Stress testing
- Usability testing
- Top-down integration testing
Answers:
- Confidentiality
- Integrity
- Authentication
- Authorization
Answers:
- A Smoke test is designed to touch every part of the application in a cursory way whereas a Sanity test is used to determine if a small section of the application is still working after a minor change
- A Smoke test adopts a shallow and wide approach whereas a Sanity test is a narrow regression test that focuses on one, or a few areas of functionality. Sanity testing is usually narrow and deep
- A Smoke test is usually unscripted whereas a Sanity test is scripted either using a written set of tests or an automated test
- A Smoke test is a normal health checkup to a build of an application before taking it to in-depth testing whereas a Sanity test is to verify whether all requirements are met or not, checking all features breadth-first
Answers:
- Slow response time
- Excessive application consumption
- Random application termination
- Failure to encrypt data
Answers:
- Repetitive testing
- Model testing
- Modular testing
- System testing
Answers:
- They help you find defects rather than failures
- They are used by developers only
- They require compilation of code
- All of the above
Answers:
- Inspection
- Black box testing
- White box testing
- Walkthrough
Answers:
- It is a high level document describing the principles, approach and major objectives of the organization regarding testing
- It is a set of test activities collected into a manageable phase of a project
- It is a collection of software and test data configured to test a program unit by running it under varying conditions and monitoring its behavior and outputs
- It is a set of several test cases for a component or a system under test
Answers:
- It allows the identification of changes in user requirements
- It facilitates timely set up of the test environment
- It reduces defect multiplication
- It allows testers to become involved early in the project
Answers:
- Control flow analysis
- Data flow analysis
- Coding standards analysis
- Function Point Analysis
Answers:
- A gradual performance slow-down leading to a non-catastrophic system halt
- A gradual performance improvement leading to a catastrophic system halt
- A gradual performance slow-down leading to a catastrophic system halt
- A gradual performance improvement to a non-catastrophic system halt
Answers:
- Smoke testing
- Marge testing
- Fuzz testing
- Operation testing
Answers:
- It takes an external perspective of the test object to derive test cases.
- It is sometimes also called as Opaque Testing, Functional Testing and Closed Box Testing.
- It uses an internal perspective of the system to design test cases based on internal structure.
Answers:
- They are used to support multi-user testing
- They capture aspects of user behavior
- They are the most frequently used types of CAST tools
- They are used to capture and playback user requirements
Answers:
- to check for logical errors
- to ensure that each code statement is executed once
- to test the functionality of the system as a whole
- to identify all paths through the software
Answers:
- Stub
- Driver
- Proxy
Answers:
- System testing
- Model testing
- Integration testing
- User acceptance testing
Answers:
- Retesting is done by programmers while Regression testing is done by testers
- Retesting checks for unexpected side-effects while Regression testing ensures that the original fault has been corrected
- Retesting ensures that the original fault has been corrected while Regression testing checks for other unexpected side-effects
- There is no difference between Regression testing and Retesting
Answers:
- Installation testing
- White-box testing
- Module testing
- Fuzz testing
Answers:
- Unit testing
- Integration testing
- Module testing
- White-box testing
Answers:
- Verification is used to check if we are doing the right thing and Validation is used to check whether we have developed the software as per the client’s requirements or not.
- Validation is used to check if we are doing the right thing and Verification is used to check whether we have developed the software as per the client’s requirements or not.
- Validation tells us what to test and Verification decides on the methodology to go about testing the application
- None of the above
Answers:
- Usability testing
- Conformance testing
- Integration testing
- System testing
Answers:
- reusability
- efficiency
- speed
- allows testing of video and mp3 files
Answers:
- An independent test team
- The software development team
- In-house users
- External users
Answers:
- Activity analysis
- Defect taxonomy for test design
- Root cause analysis
- Cleanroom software development
Answers:
- Test execution
- Test planning
- Test management
- Test design
Answers:
- Big Bang
- Top-down
- Bottom-up
- Any of the above strategies can be used
Answers:
- A Sanity test is used to determine if a small section of the application is still working after a minor change
- A Sanity test is run to check if the build of an application is stable and it can be considered for further testing
- A Sanity test is the process of testing to make sure that the older programming still works with the new changes
- All of the above are true
Answers:
- Top-down integration testing has as its major advantage that low level modules never need testing
- Alpha testing is in-house testing performed by the test team
- Equivalence partitioning is used to minimize the number of permutations and combinations of input data
- Fuzz testing provides random data to the input of a program
Answers:
- Top-down
- Big-bang
- Bottom-up
- None of the above
Answers:
- To ensure that the system will work after release
- To decide when the software is of sufficient quality to release
- To find as many bugs as possible before release
- To give information for a risk based decision about release
Answers:
- Integration testing
- Regression testing
- System testing
- User acceptance testing
No comments:
Post a Comment