1.Common Manual testing Techniques:

Black Box Testing : Tester test the software by user perspective without any coding Knowledge. We have mainly Functional and Non-Functional Testing techniques. Functional testing – Test the software matches the requirement specified in the User’s requirement document. Below are the functional Testing:

• Unit Testing o Done during the development stage by the developers. Developer test after completing development of each unit/module is working as per Requirement. This also called as Module or component testing.
• Integration Testing o Combining all the individual units/module together and test the software is working as accepted by interacting with each modules.
• System Testing o System testing is done after Integration testing to validate the software functionality end to end is working as expected.
• Smoke Testing o It is done once the tester receives the software from the developers. This testing checks whether we received the correct software from the developers.
• Sanity testing o This testing done during the release of the software. In this testing we just check main features are working as expected during the release.

Non-Functional Testing : Test the non-functional like Software speed, load, stress etc. Below are the Non-Functional Testing:

• Performance Testing o This testing used to find the speed and scalability of the software. By doing performance testing we can ensure whether the software is responding quicky for the user input.
• Usability Testing o This testing is mainly used to validate the software is understand by user perspective and easy to operate for the user.
• Security testing o Used to check the system is protected against unauthorized internal or external access.

Regression Testing: Regression testing is done once the bug/defect is fixed and the fix is not affected the existing working functionality.

Acceptance Testing: Done by end user along with the tester to check the functional is implemented as per the requirement. Below is the type of Acceptance testing o Alpha Testing: Done by client or outsource team in front of developers or testers. Minor changes can be done during this testing phase. o Beta Testing: Used to find the bugs or defects before the final release of the software. Testing done by End user.

Exploratory Testing: Performing the testing by exploring the functionality of the software without knowing the Requirement or pre-conditions.

Ad-hoc Testing: It is a informal testing. Tester tests the software without following any test case, test design technique, requirement document. Just randomly based on the intuition tester test the software.

2. Boundary Value Analysis:

It is one of test case design technique. BVA technique mainly used to validate the test data is valid or not to avoid test case failure due to invalid test. This technique is used when we have test data ranges and limits. By using this technique we validate boundary values of test data. Example of Boundary value Analysis: Consider Test Data requirement for Username textbox for login should have length of 5 to 8 character. We validate this test data by giving username with 4 characters, 5 characters, 8 characters and 9 characters.

3. Decision table:

Decision Table is the technique used to validate test data. This technique is used when we have a logical relationship if-else condition in the input.This technique is used when we have combinational inputs. Example : Valid test data when both username and password should be correct. Example : Login to a Webpage with Valid username and password and captcha In this example user should enter valid username, password, correct captcha displayed in screen and should click login button. Below is the decision table for this valid data.

4. The Future of Manual Testing in the Age of AI:

Whatever the changes comes in an industry like AI, manual testing will never destroy. Because we can automate all the possibilities like regression testing, end to end testing but few things can be validated only by human in the application to determine software is perfect. Example when we go with AI or Automation, whatever the comment we give it perform but it doesn’t check whether that is the right comment and this is needed at that particular point.