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 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
SOA
Branch testing
architecure of SOA
Monkey Testing

2. 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).
Fuzz Testing
Design based Testing
Business process-based testing
Agile Testing

3. The percentage of executable statements that have been exercised by a test suite.
Interface Testing
Branch coverage
Statement coverage
backend testing/database testing

4. 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.
End-to-end Testing
enough of testing
Basis Path Testing
Conformance Testing / Compliance Testing / Standards Testing

5. 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.
Coverage Testing
Testing best practice
Decision testing
Fuzz Testing

6. A test that exercises a feature of a product in full detail.
Boundary value analysis/ testing
Depth Testing
backend testing/database testing
Grey Box Testing

7. Depends on the schedule and risk based - business impact follow the 20-80 rules
stop testing timing
GUI Testing
backend testing/database testing
Load Testing

8. Stakeholder stakeholder satisfaction with test results report
functional testing
Defect
Mutation testing
providing information - metric

9. Testing using input values that should be rejected by the component or system
Branch
Incremental testing
Branch coverage
Invalid testing

10. Provide critical information during project
structural testing
Boundary value analysis/ testing
Business process-based testing
providing information Objective

11. 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
Dynamic Testing
Bugs
Branch
best practice

12. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules
functional testing
enough of testing
End-to-end Testing
quality assurance process improvement

13. 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
Decision table testing
High order tests
backend testing/database testing
Acceptance Testing/User Acceptance Testing

14. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Equivalence Partitioning
Bugs
Coverage Testing
Decision condition testing

15. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Gamma testing
Conformance Testing / Compliance Testing / Standards Testing
backend testing/database testing
Depth Testing

16. 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.
Context Driven Testing
organisation structure
Decision table testing
Exploratory Testing

17. Computer Aided Software Testing
CAST
High order tests
Model Based Testing
Interface Testing

18. Model-based testing refers to software testing where test cases are derived in whole or in part from a model that describes some (usually functional) aspects of the system under test.
Branch
Accessibility Testing
Model Based Testing
Incremental testing

19. 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
Boundary value analysis/ testing
Dependency Testing
Data-Driven Testing
Gamma testing

20. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Conversion Testing / Migration Testing
Exploratory Testing
Bugs
Breadth Testing

21. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
Branch coverage
stop testing timing
Fuzz Testing
white box testing

22. 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
Installation Testing
Conformance Testing / Compliance Testing / Standards Testing
Component Testing
GUI Testing

23. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Efficiency testing
Conversion Testing / Migration Testing
Fuzz Testing
Big Bang Testing

24. A white box test design technique in which test cases are designed to execute decision outcomes
Statement coverage
Keyword driven Testing
CAST
Decision testing

25. 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.
Endurance Testing
Loop Testing
GUI Testing
Keyword driven Testing

26. Test case design
Logic coverage Testing / Logic driven Testing / Structural
Defect density
Invalid testing
Load Testing

27. A white box test design technique in which test cases are designed to execute branches.
Loop Testing
GUI Testing
Branch testing
Load Testing

28. Testing the changes to an operational system or the impact of a changed environment to an operational system
Endurance Testing
architecure of SOA
Maintenance testing
test coverage

29. This term refers to making software specifically designed for a specific locality
Conformance Testing / Compliance Testing / Standards Testing
Localization Testing
Model Based Testing
GUI Testing

30. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Isolation Testing
N+ Testing
Decision condition testing
quality assurance process improvement

31. The expected results or performance characteristics that define whether the test cases passed or failed
Exploratory Testing
Acceptance criteria
Boundary value analysis/ testing
Exhaustive Testing

32. 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
backend testing/database testing
Fuzz Testing
providing information - metric
Back-to-back testing

33. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
High order tests
Gorilla Testing
Equivalence Partitioning
Decision condition testing

34. Testing whether the system is compatible with other systems with which it should communicate.
Compatibility Testing
Defect
Maintainability Testing / Serviceability Testing
Endurance Testing

35. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
black box testing
organisation structure
Monkey Testing
Testing best practice

36. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices
architecure of SOA
providing information Objective
Loop Testing
Defect density

37. 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.
black box testing
Beta Testing / Field Testing
Fault
Basis Path Testing

38. 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
Incremental testing
Exhaustive Testing
Back-to-back testing

39. 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
SOA
black box testing
Ad-hoc Testing
best practice

40. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.
Alpha Testing
Data-Driven Testing
Compatibility Testing
Mutation testing

41. Testing which covers all combinations of input values and preconditions for an element of the software under test
Dependency Testing
Exhaustive Testing
backend testing/database testing
Decision condition testing

42. executing the software
software testing
Documentation Testing
N+ Testing
Component Testing

43. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.
Load Testing
Arc Testing / Branch Testing
Basis Path Testing
software testing

44. Black-box tests conducted once the software has been integrated
Maintainability Testing / Serviceability Testing
Data-Driven Testing
quality assurance process improvement
High order tests

45. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
exploratory testing
Fuzz Testing
Interface Testing
Ad-hoc Testing

46. 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
Code coverage
N+ Testing
Dependency Testing
test coverage

47. Testing concerned with the accuracy of documentation.
Back-to-back testing
Efficiency testing
Dynamic Testing
Documentation Testing

48. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
quality assurance process improvement
backend testing/database testing
Branch coverage
Documentation Testing

49. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).
Breadth Testing
Accessibility Testing
Fault
Basis Path Testing

50. 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
best practice
Branch
Coverage Testing
architecure of SOA