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. 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
Benchmark Testing
End-to-end Testing
Keyword driven Testing
Heuristic evaluations

2. 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
Coverage Testing
Acceptance Testing/User Acceptance Testing
Endurance Testing
Ad-hoc Testing

3. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
CAST
Exploratory Testing
High order tests
Documentation Testing

4. A test that exercises a feature of a product in full detail.
architecure of SOA
white box testing
Mutation testing
Depth Testing

5. Multi-user testing geared towards determining the effects of accessing the same application code - module or database records. Identifies and measures the level of locking - deadlocking and use of single-threaded code and locking semaphores
Alpha Testing
Concurrency Testing
Acceptance criteria
best practice

6. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs
Isolation Testing
Invalid testing
Component Testing
Back-to-back testing

7. Testing concerned with the accuracy of documentation.
Exploratory Testing
Documentation Testing
enough of testing
Beta Testing / Field Testing

8. A white box testing technique that exercises program loops
Loop Testing
Equivalence Partitioning
Quality
Decision condition testing

9. Testing which covers all combinations of input values and preconditions for an element of the software under test
Interoperability testing
Exhaustive Testing
Black Box Testing / Functional Testing
Loop 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]
functional testing
Decision coverage
End-to-end Testing
organisation structure

11. 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
Decision coverage
Interface Testing
SOA

12. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
test coverage
Boundary value analysis/ testing
Decision condition testing
GUI Testing

13. executing the software
Localization Testing
Exploratory Testing
Interoperability testing
software testing

14. 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.
High order tests
Grey Box Testing
Code coverage
Boundary value analysis/ testing

15. 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
Compatibility Testing
Benchmark Testing
test coverage
organisation structure

16. 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
Efficiency testing
functional testing
Installation Testing

17. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
functional testing
AUT
Keyword driven Testing
Gamma testing

18. 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
test coverage
Arc Testing / Branch Testing
Branch testing

19. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm
stop testing timing
Agile Testing
Compatibility Testing
Localization Testing

20. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent
exploratory testing
white box testing
Back-to-back testing
Branch testing

21. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage
Branch coverage
Accessibility Testing
Basis Path Testing
Acceptance criteria

22. Kind of unit testing - internal working of software
High order tests
Maintainability Testing / Serviceability Testing
architecure of SOA
structural testing

23. Application Under Test
organisation structure
Dependency Testing
Benchmark Testing
AUT

24. Knows about the software and test - no proper plan
exploratory testing
Compatibility Testing
Isolation Testing
Defect

25. This term refers to making software specifically designed for a specific locality
Localization Testing
Depth Testing
Integration Testing
Acceptance criteria

26. Testing using input values that should be rejected by the component or system
Code coverage
N+ Testing
Exhaustive Testing
Invalid testing

27. 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
stop testing timing
Incremental testing
Mutation testing
Fuzz Testing

28. 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.
white box testing
Bottom-up Testing
test coverage
Isolation Testing

29. Checks for memory leaks or other problems that may occur with prolonged execution
Branch
Fault
Endurance Testing
N+ Testing

30. Approach to doing something that generally give good results when applied appropriately and thoughfully
Branch
Defect density
best practice
quality assurance process improvement

31. 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.
Dependency Testing
Arc Testing / Branch Testing
Keyword driven Testing
Black Box Testing / Functional Testing

32. Testing whether the system meets its specified objectives for maintainability.
Ad-hoc Testing
Maintainability Testing / Serviceability Testing
End-to-end Testing
quality assurance process improvement

33. Testing whether the system is compatible with other systems with which it should communicate.
Compatibility Testing
Equivalence partition Testing
Boundary value analysis/ testing
Design based Testing

34. Provide critical information during project
Endurance Testing
providing information Objective
Decision coverage
providing information - metric

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.
Quality
Decision testing
Basis Path Testing
Code coverage

36. Test case design
Branch
Exploratory Testing
Efficiency testing
Logic coverage Testing / Logic driven Testing / Structural

37. Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing
Integration Testing
Big Bang Testing
Interface Testing
Isolation Testing

38. Testing the changes to an operational system or the impact of a changed environment to an operational system
Maintenance testing
stop testing timing
Incremental testing
High order tests

39. 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.
Concurrency Testing
Dynamic Testing
Alpha Testing
Fuzz Testing

40. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned
Component Testing
Testing best practice
Business process-based testing
Installation Testing

41. Determine whether a system meets some specified standard. external organization as complying with the standard
Conformance Testing / Compliance Testing / Standards Testing
Concurrency Testing
Isolation Testing
Monkey Testing

42. A white box test design technique in which test cases are designed to execute branches.
SOA
Big Bang Testing
Branch testing
Authorization Testing

43. Can't see - test the functional testing - no access to code and testing is done on UI
Gorilla Testing
Statement coverage
Dynamic Testing
black box testing

44. The process of testing to determine the efficiency of a software product
Incremental testing
Documentation Testing
Efficiency testing
functional testing

45. 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
Incremental testing
white box testing
Maintenance testing
Black Box Testing / Functional Testing

46. 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)
Defect density
stop testing timing
Statement coverage
Context Driven Testing

47. The expected results or performance characteristics that define whether the test cases passed or failed
Acceptance criteria
Equivalence Partitioning
Coverage Testing
QA

48. Computer Aided Software Testing
Arc Testing / Branch Testing
white box testing
Agile Testing
CAST

49. It is a whole - is the whole process form review to plans strategy and whole thing
QA
Breadth Testing
Boundary value analysis/ testing
Back-to-back testing

50. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes
Data-Driven Testing
N+ Testing
Model Based Testing
Equivalence Partitioning