Functional Testing

                                                   

Functional System Testing Approach: 

Smoke Testing : It is a kind of quick test carried out on the application to determine whether the application is
testable or not.

Formal Testing: If you tested software application by following all preplan procedures and
proper documentation then it is called formal testing.

Adhoc Testing: If you test software without following any procedures and documentation
then it is called adhoc-testing. It is also called informal testing.

Risk Based Testing (or) Priority Based Testing: Identifying the critical functionality in the
system and testing it first

                                                                               Or

Conducting testing in the same order of priority is called risk based testing or priority based
testing.

Re- Testing: Testing functionality again or testing functionality repetitively is called re-testing.

Re-testing comes in the following 2 scenarios.

1) Testing a functionality with multiple inputs to confirm i f the business validations
are implemented or not

2) Testing a functionality on the modified build to confirm the bug fixers are made correctly or
not.

Regression Testing: It is process of identifying various features in the modified build where there is a chance of getting affected and retesting these features.

1) The new functionalities added to the existing system or modifications made to the
existing system or the bug fixes may introduce side-effects. R egression testing is
helpful to identify these side effects.

End to End Testing: Testing the overall functionalities of the system including the data integration among all the modules is called end-to-end testing.

Exploratory Testing: Exploring the application and testing the functionalities

                                                                                 (or)

Understanding system, modifying existing test cases and executing those

Monkey Testing: Testing conducted on an application unevenly or zig-zag way with an intention of finding tricky defects is called monkey testing.

Non-Functional System Testing: Validating various non functional aspects of the system such
as user interfaces, user friendliness, security, compatibility, load, stress and performance etc is
called non-functional system testing.