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. Testing using input values that should be rejected by the component or system
Decision table testing
Fuzz Testing
Invalid testing
enough of testing

2. 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
backend testing/database testing
providing information Objective
Heuristic evaluations
Dynamic Testing

3. 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
Acceptance Testing/User Acceptance Testing
Black Box Testing / Functional Testing
Branch coverage
Dependency Testing

4. 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
Decision condition testing
test coverage
Branch
organisation structure

5. Testing which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
Conversion Testing / Migration Testing
Basis Path Testing
Invalid testing

6. A white box test design technique in which test cases are designed to execute branches.
Branch testing
Quality
best practice
Installation Testing

7. Can't see - test the functional testing - no access to code and testing is done on UI
Invalid testing
Breadth Testing
black box testing
Dependency Testing

8. Test case design
Exploratory Testing
SOA
Monkey Testing
Logic coverage Testing / Logic driven Testing / Structural

9. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Benchmark Testing
Documentation Testing
Exhaustive Testing
Exploratory Testing

10. 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)
Decision condition testing
Defect density
High order tests
Business process-based testing

11. 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.
Monkey Testing
Decision condition testing
best practice
Fuzz Testing

12. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Accessibility Testing
white box testing
Documentation Testing
Acceptance criteria

13. Black-box tests conducted once the software has been integrated
High order tests
Black Box Testing / Functional Testing
Decision coverage
Authorization Testing

14. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]
backend testing/database testing
Equivalence Class
organisation structure
Gamma testing

15. 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
Alpha Testing
test coverage
Monkey Testing
Decision testing

16. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
High order tests
AUT
Isolation Testing
Logic coverage Testing / Logic driven Testing / Structural

17. executing the software
Decision condition testing
Maintainability Testing / Serviceability Testing
software testing
Installation Testing

18. 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.
Back-to-back testing
Defect
backend testing/database testing
Statement coverage

19. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
architecure of SOA
Business process-based testing
white box testing
Invalid testing

20. Knows about the software and test - no proper plan
Breadth Testing
Branch
exploratory testing
Authorization Testing

21. A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+.
N+ Testing
Interoperability testing
Branch
Equivalence Partitioning

22. Testing whether the system is compatible with other systems with which it should communicate.
Fault
Compatibility Testing
Code coverage
Depth Testing

23. 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.
Data flow Testing
AUT
organisation structure
Fault

24. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Alpha Testing
organisation structure
QA
Documentation Testing

25. 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.
Bottom-up Testing
Defect density
Beta Testing / Field Testing
Dynamic Testing

26. 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.
Fuzz Testing
Decision testing
Context Driven Testing
Exhaustive Testing

27. Computer Aided Software Testing
CAST
Conversion Testing / Migration Testing
Business process-based testing
Testing best practice

28. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table
AUT
Exhaustive Testing
Decision table testing
Localization Testing

29. 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
Bottom-up Testing
Quality
black box testing
test coverage

30. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Interoperability testing
Defect density
Grey Box Testing
Depth Testing

31. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Concurrency Testing
Testing best practice
Design based Testing
SOA

32. The percentage of decision outcomes that have been exercised by a test suite.
GUI Testing
Decision coverage
structural testing
Conversion Testing / Migration Testing

33. 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).
Ad-hoc Testing
Monkey Testing
Design based Testing
Accessibility Testing

34. 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.
Monkey Testing
Arc Testing / Branch Testing
N+ Testing
Statement coverage

35. A white box testing technique that exercises program loops
Loop Testing
Exploratory Testing
Big Bang Testing
Depth Testing

36. This term refers to making software specifically designed for a specific locality
Localization Testing
High order tests
Integration Testing
Testing best practice

37. 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.
Fuzz Testing
Basis Path Testing
Boundary value analysis/ testing
white box testing

38. Similar to black box testing - structure of test cases in order to find defects and its strutured
functional testing
providing information Objective
Exploratory Testing
Branch coverage

39. The process of testing to determine the efficiency of a software product
Monkey Testing
Efficiency testing
structural testing
Maintenance testing

40. Provide critical information during project
providing information Objective
Load Testing
Decision coverage
Bugs

41. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Endurance Testing
best practice
Development testing
Interface Testing

42. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
CAST
Exploratory Testing
Coverage Testing
Interface Testing

43. 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
Quality
best practice
Back-to-back testing
Maintenance testing

44. 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.
Fuzz Testing
SOA
Basis Path Testing
Authorization Testing

45. It is a whole - is the whole process form review to plans strategy and whole thing
QA
Invalid testing
Ad-hoc Testing
Equivalence Class

46. Testing software through executing it.
Dynamic Testing
Code coverage
SOA
Monkey Testing

47. Testing the changes to an operational system or the impact of a changed environment to an operational system
best practice
Maintenance testing
Defect density
Equivalence partition Testing

48. A test that exercises a feature of a product in full detail.
Keyword driven Testing
white box testing
Depth Testing
Acceptance criteria

49. Depends on the schedule and risk based - business impact follow the 20-80 rules
Design based Testing
Accessibility Testing
stop testing timing
Acceptance Testing/User Acceptance Testing

50. Approach to doing something that generally give good results when applied appropriately and thoughfully
Testing best practice
Logic coverage Testing / Logic driven Testing / Structural
functional testing
best practice