Lesson 1

Question 1

Black Box Testing

Answer 1

examines an application without peering into its internal structures or workings. (Zero-knowledge)

Question 2

Gray Box Testing

Answer 2

Gray Box testing is done when a tester partially knows the internal structure of an application as the algorithms used. (Some knowledge)

Question 3

White Box Testing

Answer 3

White Box testing tests the internal structures or workings of an application. (Full knowledge)

Question 4

Functional Testing

Answer 4

Testing of a software system or component based on its specifications: what the system/component does, i.e. how compliant it is with specified functional requirements. Functions are fed input and the output is examined. The internal program structure is rarely considered.

Question 5

Non-Functional Testing

Answer 5

Testing of a software application or system for its non-functional requirements: the way a system operates, rather than its specific behaviors.

Question 6

Functional Criteria:

Answer 6

Unit Testing
Integration Testing
Sanity Testing
Smoke Testing
Interface Testing
Regression Testing
Acceptance Testing

Question 7

Non-Functional Criteria:

Answer 7

Load testing
Localization testing
Performance testing
Security testing
Stress testing
Usability testing

Question 8

Unit Testing

Answer 8

Unit testing is a level of software testing where individual units/ components of a software are tested (usually made by developers).

Question 9

Integration Testing

Answer 9

Integration testing is a level of software testing where individual units are combined and tested as a group (usually made by developers, sometimes by QA engineers who specify in a certain technical area).

Question 10

System Testing

Answer 10

System testing is the process that evaluates how the various components of an application interact together in full. System testing verifies that an application performs tasks as designed. (Examples: usability, load, recovery, more)

Question 11

Acceptance testing

Answer 11

Acceptance testing is a level of software testing where a system is tested for acceptability. The purpose of this test is to evaluate the system’s compliance with the business’s requirements and assess whether it is acceptable for delivery.

Question 12

Testing Types

Answer 12

Alpha & Beta

Question 13

Alpha & Beta

Answer 13

Both are subtypes of acceptance testing.

Question 14

Alpha Testing

Answer 14

Alpha testing is performed to identify all possible issues/bugs before the product is released to end-users/public. It is usually done by designated testers/internal employees and is done early on, near the end of the development phase, and before beta testing.

Question 15

Beta Testing

Answer 15

Beta testing is done by releasing a beta version of the software to a limited number of end-users to obtain feedback on the product quality. Beta testing reduces product failure risks and provides increased product quality through customer validation.

Question 16

End To End Testing

Answer 16

End-to-end testing checks whether an application flow – from start to finish – is behaving as expected (over the full user journey). End-to-end testing is performed to identify system dependencies and to ensure that data integrity is maintained between various system components and systems.

Question 17

Smoke Testing

Answer 17

Smoke testing is performed after receiving a software build to ascertain that the critical functionalities of the program are working fine. It is executed before any detailed functional or regression tests are executed on the software build.

Question 18

Sanity Testing

Answer 18

Sanity testing is performed after receiving a software build with changes in code or functionality, to ascertain that the bugs have been fixed and that no further issues have been introduced due to these changes. (More)

Question 19

Regression Testing

Answer 19

Regression testing is performed to confirm that a recent program or code change has not adversely affected existing features, i.e. that new code changes have not caused side effects for the existing functionalities. It ensures that the old code still works once the new code changes are done.

Question 20

Performance Testing

Answer 20

Performance testing determines the speed of a computer, network or device. It checks the performance of the components of a system by passing different parameters in different load scenarios.

Question 21

Load Testing

Answer 21

Load testing simulates the actual user load on any application or website. It checks how the application behaves during normal and high loads and is applied when a development project nears completion.

Question 22

Stress Testing

Answer 22

Stress testing determines the stability and robustness of a system. It is a non-functional testing technique that uses an auto-generated simulation model to check all the hypothetical scenarios.

Question 23

Positive Testing

Answer 23

Positive testing, which uses the valid data as input, checks whether an application behaves as expected with positive inputs.

Question 24

Negative Testing

Answer 24

Negative testing ensures that your application can gracefully handle invalid input or unexpected user behavior.

Question 25

Boundary Testing

Answer 25

With this technique, test cases are designed to include values at the boundary. If the input data used is within the boundary value limits, then it is said to be positive testing. If the input data picked is outside the boundary value limits, then it is negative testing.
For example, testing user’s age, with allowed to register 18 to 150.
We check:
18, 45, 150 - positive checks inside the range.
17, 151 - negative checks outside the range.

Question 26

Bug Classification

Answer 26

1. Blocker
2. Critical
3. Major
4. Trivial
5. Minor

Question 27

Bugs Priorities

Answer 27

Severity and Priority

Question 28

Bugs Priorities - Severity

Answer 28

Severity defines the extent to which the defect can affect the software, i.e. the impact that a given defect has on the system.

Question 29

Bugs Priorities - Priority

Answer 29

Priority defines the order in which we should resolve a defect, i.e. should we fix it now or can it wait?

Question 30

Bug Reports Example:

Answer 30

Bug Title: “An attempt to access website results in 404 error”
Bug ID: 12345
Severity: HIGH
Priority: P0 (BLOCKER)
Assigned to: Developer John
Reported By: Tester Mary
Status: New
Environment details: OS: Windows 10,
Chrome version 1234.56
Steps To Reproduce: 
1) Navigate to Home Page
2) Click on the big red button
Expected Result: Page should load and work as expected
Actual Result: 404 HTTP error observed

Question 31

List of Common HTTP Status Codes

Answer 31

200 OK
300 Multiple Choices
301 Moved Permanently
302 Found
304 Not Modified
307 Temporary Redirect
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
410 Gone
500 Internal Server Error
501 Not Implemented
503 Service Unavailable
550 Permission denied