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. 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.
enough of testing
Bottom-up Testing
Statement coverage
Arc Testing / Branch Testing

2. 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.
Isolation Testing
Boundary value analysis/ testing
Alpha Testing
Code coverage

3. Depends on the schedule and risk based - business impact follow the 20-80 rules
End-to-end Testing
stop testing timing
white box testing
Isolation Testing

4. Testing software through executing it.
End-to-end Testing
Incremental testing
Dynamic Testing
architecure of SOA

5. 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
Exhaustive Testing
Quality
Load Testing
Integration Testing

6. Test case design
Exhaustive Testing
backend testing/database testing
structural testing
Logic coverage Testing / Logic driven Testing / Structural

7. 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.
Decision table testing
SOA
Authorization Testing
exploratory testing

8. The process of testing to determine the interoperability of a software product
Interoperability testing
Efficiency testing
Basis Path Testing
best practice

9. It is a whole - is the whole process form review to plans strategy and whole thing
Accessibility Testing
Loop Testing
Gamma testing
QA

10. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Loop Testing
Exploratory Testing
Authorization Testing
Accessibility Testing

11. 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
Interface Testing
Beta Testing / Field Testing
Invalid testing
Load Testing

12. Checks for memory leaks or other problems that may occur with prolonged execution
Branch testing
N+ Testing
Endurance Testing
white box testing

13. The testing of individual software components.
Component Testing
Documentation Testing
Fuzz Testing
Statement coverage

14. Testing in which test cases are designed based on variable usage within the code.
Conversion Testing / Migration Testing
Data flow Testing
Interoperability testing
Monkey Testing

15. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
best practice
Load Testing
Data flow Testing
Concurrency Testing

16. 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
Incremental testing
structural testing
Bugs
enough of testing

17. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.
Black Box Testing / Functional Testing
Design based Testing
functional testing
Context Driven Testing

18. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
enough of testing
Concurrency Testing
organisation structure
Data flow Testing

19. A white box test case design techniques that uses the algorithmic flow of the program to design tests
SOA
Beta Testing / Field Testing
Basis Path Testing
Ad-hoc Testing

20. Application Under Test
Acceptance Testing/User Acceptance Testing
Branch testing
AUT
best practice

21. Testing using input values that should be rejected by the component or system
Integration Testing
Invalid testing
Design based Testing
black box testing

22. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
Loop Testing
Branch testing
organisation structure
Defect density

23. Black-box tests conducted once the software has been integrated
Business process-based testing
Grey Box Testing
QA
High order tests

24. 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
High order tests
GUI Testing
Decision table testing

25. 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.
Code coverage
quality assurance process improvement
black box testing
Maintainability Testing / Serviceability Testing

26. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Equivalence Class
Mutation testing
Installation Testing
white box testing

27. 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)
Dependency Testing
providing information - metric
Defect density
Depth Testing

28. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.
Depth Testing
End-to-end Testing
Grey Box Testing
exploratory testing

29. 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).
Interface Testing
enough of testing
Design based Testing
Loop Testing

30. The expected results or performance characteristics that define whether the test cases passed or failed
providing information - metric
Fuzz Testing
Acceptance criteria
Data flow Testing

31. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Beta Testing / Field Testing
Decision condition testing
Defect density
Mutation testing

32. Testing in which the action of a test case is parameterized by externally defined data values - maintained as a file or spreadsheet. A common technique in Automated Testing
Data-Driven Testing
Agile Testing
Benchmark Testing
Alpha Testing

33. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
Installation Testing
AUT
black box testing

34. Testing whether the system meets its specified objectives for maintainability.
Maintainability Testing / Serviceability Testing
Accessibility Testing
Bugs
Coverage Testing

35. Provide critical information during project
providing information Objective
enough of testing
Context Driven Testing
organisation structure

36. Kind of unit testing - internal working of software
Exploratory Testing
Acceptance criteria
End-to-end Testing
structural testing

37. Knows about the software and test - no proper plan
organisation structure
exploratory testing
Arc Testing / Branch Testing
Invalid testing

38. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Gamma testing
Gorilla Testing
Conversion Testing / Migration Testing
Grey Box Testing

39. A test that exercises a feature of a product in full detail.
Defect density
Depth Testing
Ad-hoc Testing
Quality

40. 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
Documentation Testing
Equivalence Class
Benchmark Testing
Breadth Testing

41. A test suite that exercises the full functionality of a product but does not test features in detail
Conformance Testing / Compliance Testing / Standards Testing
Breadth Testing
Bottom-up Testing
Localization Testing

42. executing the software
Defect
Decision testing
Keyword driven Testing
software testing

43. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
GUI Testing
Efficiency testing
Branch coverage
Equivalence partition Testing

44. 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.
Acceptance criteria
Coverage Testing
Testing best practice
Fuzz Testing

45. 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
Isolation Testing
white box testing
Coverage Testing
Design based Testing

46. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Business process-based testing
Equivalence Class
Load Testing
Grey Box Testing

47. Determine whether a system meets some specified standard. external organization as complying with the standard
Localization Testing
Defect
Conformance Testing / Compliance Testing / Standards Testing
N+ Testing

48. This term refers to making software specifically designed for a specific locality
Model Based Testing
Defect density
Localization Testing
Depth Testing

49. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Design based Testing
Grey Box Testing
Concurrency Testing
test coverage

50. 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
Monkey Testing
Conformance Testing / Compliance Testing / Standards Testing
Defect
QA