Other Types of Functional Testing

iFour Consultancy Software Testing Training

Functional Testing

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Types of Testing : Functional ⚫Functional ⚫Regression ⚫Retest ⚫Sanity ⚫Smoke ⚫Ad-hoc ⚫Integration ⚫Acceptance testing

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Re-testing ⚍Retesting is running the previously failed test cases again on the new software to verify whether the defects posted earlier are fixed or not.

When to do Re-Testing ⚍When there is a particular bug fix specified in the Release Note, Once the development team releases the new build, then the test team has to test the already posted bugs to make sure that the bugs are fixed or not.

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Sanity Testing ⚫Sanity testing is done when as a QA we do not have sufficient time to run all the test cases, be it functional testing, UI, OS or browser testing. ⚫Sanity testing as a test execution which is done to touch each implementation and its impact but not thoroughly or in-depth, it may include functional, UI, version etc. testing depending on the implementation and its impact. ⚫The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing. ⚫This mainly includes verification of business rules, functionality. ⚫Bottom-Up approach. https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Smoke Testing ⚫Smoke testing is type of software testing whereas QA team need to determines whether deployed build is stable or not. And upon it team can get confirmation that they can proceed with further testing or not. ⚫In simple terms, we are verifying whether the important features are working and there are no showstoppers in the build that is under testing. ⚫Smoke testing is used to test all areas of the application without going into too deep. ⚫It is done when the new functionalities of software are developed and integrated with existing build that is deployed in QA/staging environment. It ensures that all critical functionalities are working correctly or not. https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Basic understanding between Smoke & Sanity ⚫Smoke testing is done when the initial release of module comes. We check whether system’s major functionality is working fine and whether we find any showstopper bug. In the initial stage of build, the system is not stable. ⚫When we raise defects and developer fixes them and gives us new builds over a certain period of time and that time we say when system is enough stable as well there is least possibility to fail a test case, that time we do Sanity testing. ⚫Smoke testing of the software is to check build is stable to accepted for through software testing & done it in early stage. Sanity testing of the software is to ensure whether the requirements are met or not.

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Ad-hoc Testing ⚍ Ad hoc testing is type of software testing to perform testing without planning and documentation. ⚍ There are different types of Ad-hoc testing and they are listed as below: Buddy Testing

Two buddies mutually work on identifying defects in the same module. Mostly one buddy will be from development team and another person will be from testing team. Buddy testing helps the testers develop better test cases and development team can also make design changes early. This testing usually happens after Unit Testing completion.

Pair testing

Two testers are assigned modules, share ideas and work on the same machines to find defects. One person can execute the tests and another person can take notes on the findings. Roles of the persons can be a tester and scriber during testing.

Monkey Testing

Randomly test the product or application without test cases with a goal to break the system.

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Integration Testing ⚫Integration testing is a type of software testing where multiple modules/features/units are combined and test together as a group. ⚫Purpose of this type of testing is when two or more units combined as a integrate functionality which were working fine as a individually but is it working still fine after integrating units or not. ⚫Integration testing take part after unit testing and before validation testing. ⚫At the time of Agile module development, there are wide chances of change in requirements by the clients. These new requirements may not be unit tested and hence system integration Testing becomes necessary.

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Acceptance Testing ⚫This type of testing done as final phase testing before releasing product. ⚫The main purpose of this testing is to validate the end to end business flow and it has met the required criteria for delivery to end user or not. ⚫Usually, Black Box Testing method is used in Acceptance Testing. Testing does not normally follow a strict procedure and is not scripted but is rather ad-hoc. ⚫User Acceptance Testing (Also known as Beta Testing) is performed by the end users of the software. They can be the customers themselves or the customers’ customers.

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Acceptance Testing ⚫There are various forms of acceptance testing: ⚫Internal Acceptance Testing (Alpha Testing) is performed by members of the organization who are not directly involved in the project. ⚫External Acceptance Testing is performed by people who are not employees of the organization that developed the Product. ⚫User Acceptance Testing (Beta Testing) is performed by the end users of the Product.

They can be the customers themselves or the customers’ customers.

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management

Thank you

https://www.ifourtechnolab.com/asp-dot-net-enterprise-content-management