Go to previous article – Agile Management – Shifting to Agile Testing

Learn how it works – Software Testing Methodologies

Software Testing is the assessment of software that is being developed, in order to check if it’s capable of delivering the intended results. There are different types of Software Testing Methodologies used in the field of Software Testing and quality assurance, Testing Methods are tactics for testing, they can go anywhere from unit testing to system testing and more.

However there is no formally recognized form of Testing Methodologies, but here are some common Software Testing Methodologies:

Unit testing –

Unit testing is the act of testing software at the most basic (object) level and it is usually the first to be carried out. Read more about Unit testing in here!

Acceptance testing – 

User Acceptance Testing is also known as acceptance tests, it is usually the last one to be carried out. It is used to ensure that the software that has been developed meets all customer requirements.The term “smoke test” is a informal term that comes from when machines were built, engineers would power them up and just let them run, looking for smoke as a sign of serious problems.

There are two types of acceptance testing, one is carried out by the members of the development team, known as internal acceptance testing or Alpha testing, and the other that is carried out by the customer, known as external acceptance testing, in case the test is performed by the end users of the software, it is known as user acceptance testing or Beta testing.

Functional testing –

Functional Testing takes a product feature and tests all of the functionality contained within that feature, in other terms, it is also known as Black-box testing and it is carried out without any knowledge of the internal working of the system. The tester will stimulate the software to the user environment by providing different inputs and testing the outputs.

White-Box testing –

White-Box testing, unlike the black-box one, takes into account the internal functioning and logic of the code, to carry out this test. The tester has knowledge of the code, so as to find out the exact part of the code that is having errors.

System testing –

System testing is the project as a collective system, it generally combines multiple features into an end-to-end process or scenario.

Performance testing –

Performance testing tests an application’s performance characteristics, be it file size, concurrent users, or mean-time-to-failure.

Security testing –

Security testing is a collection of tests focused on probing an application’s security, or its ability to protect user assets. It is considered a nonfunctional test an application’s security is one of the main concerns of the developer, where they test the software for confidentiality, authentication, availability, and non-repudiation.

The main goal of these individual tests is to prevent any unauthorized access to the software code.

Stress testing –

Software stress testing is a method where the software is exposed to conditions that surpass the software’s normal working conditions; this test determines the stability of the entire system.

Compatibility test –

When the software is tested for its compatibility with an external interface, such as operating systems, hardware platforms and web browsers, it is called Compatibility Test.

These are some of the most common Software Testing Methodologies, however as it was stated before there are many others that give additional results about the ability of the software to produce the intended results.

Read about Performance Testing