Manual Testing

Type of testing

There are 2 main types, functional and non-functional:

Functional: Which tests the real-world, business application of a software solution. As the name implies, this type of testing verifies that functional aspect of the application is functioning as expected.

Non-functional: Which tests the remaining requirements of the software (for example performance, data storage, etc.)

Aside from the above mentioned types of testing; Smoke Tests, Integration Tests, Regression Tests, Performance Tests, Acceptance Tests, etc. are also common.

Smoke Tests: Smoke tests are a type of Functional test that only covers the most crucial features of a software solution to ensure that it could be further tested without “catching fire,” hence the name Smoke Tests.

Integration Tests: Integration tests take all the individual pieces and functionalities of a software solution and test them together as a whole to guarantee smooth operation between all of them.

Regression Tests: Regression tests run a combination of Functional and Non-functional tests to check if the software has “regressed” after a given change.

Performance Tests: Performance tests are often Non-functional tests that help testers evaluate criteria like responsiveness and stability as the software handles load and stress.

Acceptance Tests: Acceptance tests are functional tests that determine how acceptable the software is to the end-users. This is the final test a solution must pass before it could be released.

Phase of testing

Unit: As the name implies, this phase tests the individual components, or units, of software. Unit testing is the very first phase of testing, usually done manually by developers before handing the software off to testers, but it could also be automated.

API: Application Programming Interface (or API for short) acts as the “middleman” between all of the systems that your software uses, and thus, is then tested after the development process to ensure smooth integration between systems and software. This phase of testing is fairly flexible; it could be conducted either before or after the UI phase, which we will go over shortly, and by either the development or the testing team.

UI: Last but not least, User Interface (AKA UI) is what the end-users see and interact with and, thus, is usually tested at the very end of the process. This phase of testing is run by testers after the UI of the application has been drafted for the most authentic replication of user experience possible. This is where the business logic of the software is examined and optimized, which also falls under the Functional test classification.