Test your basic knowledge |

Software Testing And Qa

Subject : it-skills

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. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Invalid testing
Development testing
Bottom-up Testing
Equivalence partition Testing

2. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Grey Box Testing
Accessibility Testing
Isolation Testing
Documentation Testing

3. 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.
Gorilla Testing
Dependency Testing
Authorization Testing
Conformance Testing / Compliance Testing / Standards Testing

4. Black-box tests conducted once the software has been integrated
Heuristic evaluations
Mutation testing
Monkey Testing
High order tests

5. They arise from mistakes and errors made by people in either a program's source code or its design that prevents it from working correctly or produces an incorrect result
Mutation testing
Incremental testing
Bugs
Model Based Testing

6. A service oriented architecture (SOA) is a design model which relies on a collection of loosely coupled self contained services that communicate with each other through the internet and can be called from multiple clients in a standard fashion
Maintenance testing
Branch coverage
SOA
stop testing timing

7. A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification
Equivalence Class
Context Driven Testing
Maintainability Testing / Serviceability Testing
End-to-end Testing

8. 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.
Alpha Testing
Fuzz Testing
Data flow Testing
Endurance Testing

9. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Statement coverage
Business process-based testing
white box testing
Maintenance testing

10. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Agile Testing
organisation structure
Maintainability Testing / Serviceability Testing
SOA

11. Testing in which test cases are designed based on variable usage within the code.
Equivalence Partitioning
Business process-based testing
Data flow Testing
Acceptance criteria

12. 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
architecure of SOA
Beta Testing / Field Testing
Development testing
Efficiency testing

13. Knows about the software and test - no proper plan
Coverage Testing
exploratory testing
Isolation Testing
Dependency Testing

14. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
CAST
Component Testing
Interface Testing
Ad-hoc Testing

15. A test suite that exercises the full functionality of a product but does not test features in detail
Breadth Testing
Fault
black box testing
Gamma testing

16. 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
Mutation testing
enough of testing
Gorilla Testing
Model Based Testing

17. Testing whether the system meets its specified objectives for maintainability.
providing information - metric
Acceptance criteria
Heuristic evaluations
Maintainability Testing / Serviceability Testing

18. 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).
Dynamic Testing
Design based Testing
architecure of SOA
Decision coverage

19. 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.
functional testing
Fault
Boundary value analysis/ testing
Bottom-up Testing

20. Kind of unit testing - internal working of software
Decision table testing
Back-to-back testing
Gorilla Testing
structural testing

21. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)
End-to-end Testing
Installation Testing
Exploratory Testing
Defect density

22. A white box test design technique in which test cases are designed to execute branches.
Branch testing
Documentation Testing
Concurrency Testing
Bottom-up Testing

23. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality
Data-Driven Testing
Dependency Testing
Exploratory Testing
Equivalence Class

24. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.
Authorization Testing
Interoperability testing
Defect
Context Driven Testing

25. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
N+ Testing
exploratory testing
white box testing
backend testing/database testing

26. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
backend testing/database testing
Heuristic evaluations
functional testing
enough of testing

27. The process of testing to determine the efficiency of a software product
Dynamic Testing
Context Driven Testing
N+ Testing
Efficiency testing

28. Testing using input values that should be rejected by the component or system
Exploratory Testing
Documentation Testing
Development testing
Invalid testing

29. 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
Incremental testing
Branch coverage
Coverage Testing
structural testing

30. 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
Black Box Testing / Functional Testing
Load Testing
Equivalence Partitioning
Back-to-back testing

31. A white box testing technique that exercises program loops
Localization Testing
Quality
Loop Testing
enough of testing

32. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
GUI Testing
Ad-hoc Testing
Depth Testing
Branch coverage

33. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Big Bang Testing
Equivalence partition Testing
Decision table testing
Maintainability Testing / Serviceability Testing

34. A scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.
Keyword driven Testing
Branch coverage
Gorilla Testing
Decision condition testing

35. 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.
Alpha Testing
SOA
Compatibility Testing
Code coverage

36. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
AUT
functional testing
GUI Testing
Acceptance criteria

37. The percentage of decision outcomes that have been exercised by a test suite.
Decision coverage
Context Driven Testing
white box testing
quality assurance process improvement

38. Computer Aided Software Testing
CAST
providing information Objective
Fuzz Testing
Decision testing

39. Can't see - test the functional testing - no access to code and testing is done on UI
black box testing
Defect
Context Driven Testing
Data flow Testing

40. 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
Context Driven Testing
functional testing
test coverage
Decision table testing

41. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Benchmark Testing
Localization Testing
Testing best practice
organisation structure

42. This term refers to making software specifically designed for a specific locality
Logic coverage Testing / Logic driven Testing / Structural
Localization Testing
Conversion Testing / Migration Testing
architecure of SOA

43. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
Mutation testing
Ad-hoc Testing
Concurrency Testing
GUI Testing

44. Testing software through executing it.
Localization Testing
stop testing timing
Accessibility Testing
Dynamic Testing

45. 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.
Decision testing
Bottom-up Testing
Gamma testing
Ad-hoc Testing

46. Provide critical information during project
Big Bang Testing
providing information Objective
Dependency Testing
Basis Path Testing

47. A test case design technique for a component in which test cases are designed which include representatives of boundary values - the defined limits of an output domain.
Conversion Testing / Migration Testing
best practice
Boundary value analysis/ testing
Isolation Testing

48. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Alpha Testing
Conformance Testing / Compliance Testing / Standards Testing
Decision table testing
Equivalence Partitioning

49. 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
software testing
providing information Objective
SOA
Branch

50. Test case design
Logic coverage Testing / Logic driven Testing / Structural
Bugs
Benchmark Testing
Branch coverage