Software Testing And Qa

Instructions:

• Answer 50 questions in 15 minutes.
• If you are not ready to take this test, you can study here.
• Match each statement with the correct term.
• Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. Testing which covers all combinations of input values and preconditions for an element of the software under test
Breadth Testing
Branch coverage
CAST
Exhaustive Testing


2. Testing in which test cases are designed based on variable usage within the code.
Development testing
architecure of SOA
Bugs
Data flow Testing


3. A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point - each possible branch be executed at least once.
structural testing
Coverage Testing
Branch coverage
Arc Testing / Branch Testing


4. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
Gamma testing
Defect density
Agile Testing
software testing


5. A test that a user/sponsor and manufacturer/producer jointly perform on a finished - engineered product/system through black-box testing - as functional test & beta test & QA test & application test & confidence test & final test or end user test
AUT
Acceptance Testing/User Acceptance Testing
Authorization Testing
Statement coverage


6. Once the alpha phase is complete development enters the beta phase. Versions of the software known as beta-versions are released to a limited audience outside of the company to ensure that the product has few faults or bugs. black box
Beta Testing / Field Testing
CAST
Decision testing
Branch testing


7. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Defect
Agile Testing
Big Bang Testing
Design based Testing


8. Testing a system or an Application on the fly - i.e just few tests here and there to ensure the system or an application does not crash out
Development testing
Back-to-back testing
Monkey Testing
Interface Testing


9. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Isolation Testing
Interface Testing
stop testing timing
Acceptance criteria


10. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Gorilla Testing
Defect density
Grey Box Testing
white box testing


11. Depends on the schedule and risk based - business impact follow the 20-80 rules
software testing
Statement coverage
Acceptance criteria
stop testing timing


12. A test suite that exercises the full functionality of a product but does not test features in detail
structural testing
Benchmark Testing
Breadth Testing
Decision condition testing


13. Testing whether the system meets its specified objectives for maintainability.
Logic coverage Testing / Logic driven Testing / Structural
Maintainability Testing / Serviceability Testing
High order tests
Agile Testing


14. A test that exercises a feature of a product in full detail.
Equivalence partition Testing
Depth Testing
Coverage Testing
Defect density


15. An approach to integration testing where the lowest level components are tested first - then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.
Bugs
Interoperability testing
Bottom-up Testing
Dynamic Testing


16. Checks for memory leaks or other problems that may occur with prolonged execution
N+ Testing
Endurance Testing
Big Bang Testing
Maintainability Testing / Serviceability Testing


17. Similar to black box testing - structure of test cases in order to find defects and its strutured
Defect
Mutation testing
Dynamic Testing
functional testing


18. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Isolation Testing
Incremental testing
Agile Testing
GUI Testing


19. This term refers to making software specifically designed for a specific locality
Loop Testing
Localization Testing
Conformance Testing / Compliance Testing / Standards Testing
structural testing


20. Testing whether the system is compatible with other systems with which it should communicate.
Coverage Testing
Compatibility Testing
exploratory testing
Maintainability Testing / Serviceability Testing


21. An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.
structural testing
Code coverage
Big Bang Testing
quality assurance process improvement


22. Testing one particular module - functionality heavily
Mutation testing
Monkey Testing
Gorilla Testing
white box testing


23. Defined as any testing that occurs outside of the development environment. installed on. simply appear to be to run a setup program - can be used with confidence
Decision testing
Exhaustive Testing
Dynamic Testing
Installation Testing


24. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program path is available
Acceptance Testing/User Acceptance Testing
exploratory testing
Branch
Maintainability Testing / Serviceability Testing


25. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases
test coverage
Keyword driven Testing
Maintenance testing
Authorization Testing


26. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Development testing
Benchmark Testing
Grey Box Testing
Dynamic Testing


27. Testing concerned with the accuracy of documentation.
Heuristic evaluations
organisation structure
QA
Documentation Testing


28. Approach to doing something that generally give good results when applied appropriately and thoughfully
AUT
providing information Objective
best practice
Gamma testing


29. Provide critical information during project
providing information Objective
Statement coverage
Data flow Testing
exploratory testing


30. Informal method of usability inspection in the field of human-computer interaction. identifying the usability problems . involves evaluators examining the interface and judging its compliance
software testing
Heuristic evaluations
Arc Testing / Branch Testing
Defect


31. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or
Isolation Testing
Black Box Testing / Functional Testing
Beta Testing / Field Testing
Coverage Testing


32. Testing using input values that should be rejected by the component or system
Branch
Monkey Testing
Ad-hoc Testing
Invalid testing


33. A white box testing technique that exercises program loops
Interface Testing
structural testing
Loop Testing
Beta Testing / Field Testing


34. Computer Aided Software Testing
Logic coverage Testing / Logic driven Testing / Structural
Decision condition testing
enough of testing
CAST


35. Application Under Test
backend testing/database testing
Grey Box Testing
AUT
Decision testing


36. The totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs." defined by ISO 8402 1986
Incremental testing
Quality
providing information Objective
Statement coverage


37. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.
Maintenance testing
Branch testing
Interface Testing
Fuzz Testing


38. An accidental condition that causes the failure of a component in the implementation model to perform its required behavior. A fault is the root cause of one or more defects identified by observing one or more failures.
N+ Testing
Data flow Testing
Fault
software testing


39. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies
Back-to-back testing
Bugs
enough of testing
CAST


40. Root cause analyst - base of the problem - customer satisfaction report
architecure of SOA
Boundary value analysis/ testing
Acceptance Testing/User Acceptance Testing
quality assurance process improvement


41. A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations
Acceptance Testing/User Acceptance Testing
Mutation testing
best practice
Gorilla Testing


42. Coverage testing is concerned with the degree to which test cases exercise or cover the logic (source code) of the software module or unit. It is also a measure of coverage of code lines & code branches and code branch combinations
Coverage Testing
Invalid testing
Decision table testing
black box testing


43. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Acceptance Testing/User Acceptance Testing
Exhaustive Testing
Dependency Testing
Defect density


44. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
test coverage
Keyword driven Testing
exploratory testing
Business process-based testing


45. The testing of individual software components.
Business process-based testing
Statement coverage
Component Testing
Equivalence Partitioning


46. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Exploratory Testing
white box testing
black box testing
N+ Testing


47. Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields & Cookie security and Lockout testing . permitting unauthorised access.
Authorization Testing
Dynamic Testing
Big Bang Testing
AUT


48. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).
Mutation testing
Equivalence partition Testing
Design based Testing
enough of testing


49. The percentage of decision outcomes that have been exercised by a test suite.
functional testing
Decision coverage
quality assurance process improvement
Big Bang Testing


50. The expected results or performance characteristics that define whether the test cases passed or failed
Concurrency Testing
Acceptance criteria
Exploratory Testing
Alpha Testing