Termonology

Question 1

Testing

Answer 1

The process of verifying and validating that a software is bug free and meets all requirements with handling all the exceptional and boundary cases.

Question 2

Test Case

Answer 2

A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.

Question 3

Functional Testing

Answer 3

System is tested against the functional requirements/specifications. The System is functioning as it should.

Question 4

Compatibility Testing

Answer 4

Type of Software testing to check whether your software is capable of running on different hardware, operating systems, applications, network environments or Mobile devices.

Question 5

Localization Testing

Answer 5

Product is checked to assure that it behaves according to the local culture or settings. (language, currency, date and time format).

Question 6

Performance Testing

Answer 6

a type of testing that determines the speed, responsiveness and stability of a software program or device under a workload. It is a type of automated testing (next level).

Question 7

Stress Testing

Answer 7

a type of testing that determines the stability and durability of the system.

Question 8

Load Testing

Answer 8

is the process that simulates actual user load on any application or website.

Question 9

Black-Box Testing

Answer 9

You don’t know (and you don’t care) how the code works. This is a type of testing where an application is tested based on the inability to access the code an no knowledge of the software’s internal code.

Question 10

White Box Testing

Answer 10

Testing where you have knowledge of the code and internal app structure.

Question 11

Gray Box Testing

Answer 11

Test Technique of a software or app with partial knowledge of the code

Gray Box combines Black box and White box testing.
Black + White = Gray

Question 12

Security Testing

Answer 12

Testing to determine if a system protects data and maintains functionality

Question 13

Ad Hoc Testing ( Monkey Testing)

Answer 13

Software testing without any planning and documentation. Tests are done informally and randomly without any formal procedure or expected results.

Question 14

UI (GUI) Testing

Answer 14

Testing performed by interacting with the software under test via the graphical user interface.

Question 15

What is Software Quality Assurance?

Answer 15

From a QA viewpoint, its about Software being up to requirements.
Software QA is the process of monitoring and improving all activities associated with software development.

Question 16

What is Software Testing?

Answer 16

Software testing is a process of executing a program or application with the intent of finding software bugs.

Question 17

What is Smoke Testing

Answer 17

A quick test after the software has had repairs or a new build is released.

Question 18

Sanity Testing

Answer 18

A quick test performed after receiving a software build with minor changes in the code or functionality.

Question 19

What is a test cycle?

Answer 19

A test cycle is a container for tests and test suites that spans multiple users and projects.

Question 20

What is a Smoke Test Suite?

Answer 20

A smoke test suite combines a number of smoke tests into a small suite of tests

Question 21

Regression Testing

Answer 21

Testing in which test cases are re-executed to check if the functionality still works and that the new changes have not made new bugs

or

Regression Testing is a type of testing that is done to verify that a software code change does not impact the existing functionality of the product

Question 22

When should you perform Regression testing?

Answer 22

Regression Testing is usually performed after the verification of changes or new functionality

Question 23

What is a test plan

Answer 23

The test plan is a document described for software testing scope and activities.

It is a document describing scope, approach, resources, and schedule of intended test activities.

Question 24

E2E testing

Answer 24

End-to-end testing is a technique used to test whether the flow of an application is behaving as expected right from start to finish.