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. It is a whole - is the whole process form review to plans strategy and whole thing
Defect density
QA
N+ Testing
Boundary value analysis/ testing

2. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers
Efficiency testing
providing information Objective
Development testing
Monkey Testing

3. 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.
Fuzz Testing
Design based Testing
Accessibility Testing
Localization Testing

4. Testing software through executing it.
Business process-based testing
Dynamic Testing
Model Based Testing
Defect

5. Approach to doing something that generally give good results when applied appropriately and thoughfully
Documentation Testing
best practice
Decision condition testing
enough of testing

6. Stakeholder stakeholder satisfaction with test results report
providing information - metric
Heuristic evaluations
Boundary value analysis/ testing
Dynamic Testing

7. 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
Branch coverage
Black Box Testing / Functional Testing
Breadth Testing

8. The process of testing to determine the efficiency of a software product
Efficiency testing
AUT
Data flow Testing
Component Testing

9. The testing of individual software components.
Component Testing
Interoperability testing
Decision condition testing
providing information - metric

10. 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.
Integration Testing
Interface Testing
Authorization Testing
Interoperability testing

11. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.
Load Testing
Exploratory Testing
Design based Testing
Agile Testing

12. Testing whether the system is compatible with other systems with which it should communicate.
Equivalence Partitioning
Defect density
Integration Testing
Compatibility Testing

13. 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
High order tests
Model Based Testing
test coverage
Acceptance Testing/User Acceptance 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.
Boundary value analysis/ testing
Data flow Testing
GUI Testing
Ad-hoc Testing

15. 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
Incremental testing
architecure of SOA
Data flow Testing
Decision testing

16. 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
Fault
Acceptance Testing/User Acceptance Testing
Incremental testing

17. Checks for memory leaks or other problems that may occur with prolonged execution
Loop Testing
Benchmark Testing
Endurance Testing
Acceptance criteria

18. 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
Gamma testing
Context Driven Testing
Beta Testing / Field Testing

19. 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
Branch coverage
Ad-hoc Testing
Monkey Testing
Accessibility Testing

20. Root cause analyst - base of the problem - customer satisfaction report
quality assurance process improvement
Depth Testing
Alpha Testing
Gorilla Testing

21. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.
Gamma testing
Accessibility Testing
structural testing
End-to-end 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]
Incremental testing
organisation structure
Conformance Testing / Compliance Testing / Standards Testing
End-to-end Testing

23. A white box test case design techniques that uses the algorithmic flow of the program to design tests
Conversion Testing / Migration Testing
best practice
Basis Path Testing
QA

24. 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
Statement coverage
Documentation Testing
stop testing timing
Concurrency Testing

25. Testing the changes to an operational system or the impact of a changed environment to an operational system
Maintenance testing
Equivalence Class
Decision condition testing
architecure of SOA

26. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.
backend testing/database testing
Equivalence partition Testing
Depth Testing
Development testing

27. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes
Business process-based testing
Logic coverage Testing / Logic driven Testing / Structural
Equivalence partition Testing
Isolation Testing

28. 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
Benchmark Testing
Code coverage
Component Testing
Bugs

29. Kind of unit testing - internal working of software
white box testing
structural testing
Beta Testing / Field Testing
Defect density

30. 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.
Dependency Testing
End-to-end Testing
providing information Objective
Incremental testing

31. Testing which covers all combinations of input values and preconditions for an element of the software under test
Exhaustive Testing
SOA
stop testing timing
Logic coverage Testing / Logic driven Testing / Structural

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

33. The process of testing to determine the interoperability of a software product
Interoperability testing
test coverage
Equivalence partition Testing
GUI Testing

34. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications
Equivalence partition Testing
best practice
organisation structure
GUI Testing

35. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.
Interface Testing
Invalid testing
Load Testing
Business process-based testing

36. The percentage of executable statements that have been exercised by a test suite.
Statement coverage
best practice
Basis Path Testing
Breadth Testing

37. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database
Code coverage
Exploratory Testing
Installation Testing
Grey Box Testing

38. A test suite that exercises the full functionality of a product but does not test features in detail
Breadth Testing
stop testing timing
black box testing
Back-to-back testing

39. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Conversion Testing / Migration Testing
QA
Black Box Testing / Functional Testing
stop testing timing

40. Test case design
Logic coverage Testing / Logic driven Testing / Structural
Compatibility Testing
stop testing timing
providing information Objective

41. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes
Heuristic evaluations
Decision condition testing
Design based Testing
Basis Path Testing

42. 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.
Model Based Testing
Heuristic evaluations
Quality
enough of testing

43. 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
Maintenance testing
software testing
Acceptance Testing/User Acceptance Testing
Black Box Testing / Functional Testing

44. 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
Invalid testing
Decision table testing
Data flow Testing
Code coverage

45. 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
Accessibility Testing
Quality
Isolation Testing
High order tests

46. Testing concerned with the accuracy of documentation.
providing information Objective
Model Based Testing
Documentation Testing
exploratory testing

47. 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.
SOA
Coverage Testing
best practice
Arc Testing / Branch Testing

48. 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
Heuristic evaluations
best practice
Integration Testing
Depth Testing

49. Computer Aided Software Testing
black box testing
CAST
functional testing
Maintenance testing

50. Testing in which test cases are designed based on variable usage within the code.
Data flow Testing
Loop Testing
Quality
AUT