Manual Testing Tutorials - What is manual testing

What is Manual Testing?

Software testing is done to find the process or method of finding errors / errors in the software application or program known to enable the application to function according to the need of the end users. This is the prime responsibility in manual testing jobs.

Manual testing involves manually testing a software without using any automated tools or any scripts as we create selenium script for automation testing. Thus, the manual tester plays the role of a end user who tests the software to identify any unexpected behavior, bugs or defects. There are various steps for manual testing such as unit testing, integration testing, system testing, and user acceptance testing.

Where software testing is done to find the process or method of finding errors in the software application or program known to enable the application to function according to the need of the end users.

According to the definition of manual testing - the process of analyzing software items to detect differences between existing and required conditions and to evaluate the features of software items.

Automation testing is also part of software testing where automation testing tools are used to perform actions automatically. Manual testing interview questions basically comes from basic of manual testing where many skilled testers struggle. Lets discus below types of manual testing or Manual testing tutorial.

Methods of Software testing

1. White Box Testing:

White-box testing is also called open-box testing or glass box testing . White-Box Testing is a detailed examination of internal logic and code structure. The tester monitors the source code and finds out which unit / part of the code is behaving incorrectly. White-Box Testing is used to design the test case of the programming scheme along with the internal perspective of the system. This testing is usually done at the unit level.

2. Black Box Testing:

It is also called Behavioral Testing. This is the technique of manual testing without any knowledge about the internal work of the application is called black-box testing. In this manual tester is not aware of the architecture of the system and don't have much coding knowledge.

Typically, while performing black-box testing, the tester interacts with the user interface of the system by giving input and checking its output, without knowing how and where the input is handled.

3. Gray-Box Testing:

Gray-Box Testing is a technique for testing applications with limited knowledge of the application's internal functionality. In software testing, the more you know the tester phrase, the better the application can be tested. Unlike black-box testing, where the tester only tests the user interface of the application. In gray-box testing, the tester has access to the design document and database. With this knowledge, a tester can create better test data and test scenarios.

Types of Software Testing

A. Functional Testing:

It is a type of black-box testing that is based on the specifications of the software being tested. The application is tested by providing input and then checking the results which should correspond to the intended functionality for it. Functional testing of a software is performed on a complete, integrated system, which evaluates system compliance according to specific requirements.

Type of Functional Testing

1. Integration Testing

Integration testing is defined as testing the combined parts of an application to determine whether they function correctly.Integration testing can be done in two ways: bottom-up integration testing, top-down integration testing and mixed integration testing.

2. Unit Testing

Unit Testing is done to check if different modules of the source code are working properly. That is, in the developer's environment, each unit of the application is tested separately by the developer.The goal of unit testing is to separate each part of the program and to check that all the requirements.

3. System Testing:

System testing fully tests the system. Once all components are integrated, the entire application is rigorously tested to see that it satisfies the specified quality standard. This type of testing is done by a specialized testing team.

4. Regression Testing

Whenever a software application changes, it is quite possible that other applications within the application have also been affected by this change.Regression testing is done to verify that the fixed bug is not violating other functionality or business rules.

5. Acceptance Testing

This testing is done to get customer sign-off, so that the software can be delivered and payment is received.

B. Non-Functional Testing:

This is based on testing an application with non-functional features. Non-functional testing involves testing software from requirements that are non-functional in nature but are important for performance, security, user interface, etc.

1. Performance Testing:

It is mostly used in software to identify any bottlenecks or performance problems rather than finding bugs.There are various reasons why the software performance is low - Network delay , Load balancing between servers, Data rendering, speed, capacity or Stability.

2. Load Testing:

It is the process of examining the behavior of software by applying the maximum load in terms of accessing the software and manipulating large input data. This can be done in both normal and extreme load conditions. This type of testing identifies the software's maximum capacity and its behavior at peak times.

3. Security Testing

Security testing involves testing the software to identify any defects in security. This is perform on applications to check if it is free from any risk , vulnerabilities or threats.

Manual testing interview questions will be asked maximum of the time from above discussed topics. We will soon be posting manual testing resume which will help in finding relevant manual testing job.

For Automation testing resume check out here : Selenium Resume

. 

• Tweet
• Share
• Share
• Share
• Share