DEV Community: Chendur Murugan S

What is Manual Testing? What are the benefits and drawbacks of Manual testing? Give examples in support of your answer.

Chendur Murugan S — Fri, 01 Mar 2024 03:13:06 +0000

Manual Testing:

Manual Testing is a software testing process in which test cases are executed manually without using any automated tool.
All test cases are executed by the tester manually according to the end user's perspective.
It ensures whether the application is working, as mentioned in the requirement document or not.
Manual testing is one of the most fundamental testing processes as it can find both visible and hidden defects of the software.
The difference between expected output and output, given by the software, is defined as a defect.
Manual testing is mandatory for every newly developed software before automated testing. This testing requires great efforts and time, but it gives the surety of bug-free software.

Advantages of Manual Testing

It doesn't require programming knowledge while using blackbox method.
It is used to test dynamically changing GUI designs.
Tester interacts with software as a real user so that they are able to discover usability and user interface issues.
It ensures that the software is a hundred percent bug free.
It is cost effective.
Easy to learn for new testers.

Disadvantages of Manual Testing

It requires a large number of human resources.
It is very time consuming.
Tester develops test cases based on their skills and experience. There is no evidence that they have covered all functions or not.
Test cases cannot be used again. Need to develop separate test cases for each new software.
It does not provide testing on all aspects of testing.
Since two teams work together, sometimes it is difficult to understand each other's motives, it can mislead the process.

Examples of Manual Testing
1) Manual Insurance Application Testing

Testers examines the policy creation functionality, ensuring that a new policy can be successfully created with accurate information and stored in the correct system.

Log in to the insurance application with valid credentials.
Navigate to the policy creation section
Enter the required policy details, such as policy type, insured party information, coverage details, and premium amount.
Provide valid and appropriate inputs for each field, ensuring data accuracy.
Save the policy.

Expected Result

The policy should be created successfully and a confirmation message or notification should be displayed.
The created policy should have accurate and consistent information as provided during the policy creation process.
The new policy is stored and accessible in the insurance application for further processing and management.
The right information is presented in the frontend and backend.

Difference between Functional Testing and Non Functional Testing with Examples

Chendur Murugan S — Sun, 18 Feb 2024 04:05:05 +0000

In Software Development Life Cycle QA testing is one of the fundamental steps to build a quality product.
Different aspects of the Software is tested via different tests which can be divided into 1) Functional testing
2) Non functional testing

Functional Testing 1) Functional testing specifies that the operation of a program or mobile application performs according to business requirements. 2) Functional testing are usually performed manually and before non-functional tests. 3) The tester provides the specific input to the program and compares its result with the expected output. Functional testers don't care about source code, they only focus on checking the functionality. 4) Functional testing is necessary to ensure that the product is free of any bugs or vulnerabilities.

-Non-Functional Testing
1) Non-functional testing covers all the aspects not covered by functional testing. It covers the performance, availability, scalability and reliability of the software.
2) It is performed to ensure that interests of the end user is fulfilled. It makes sure the Product/software doesn't fail in the market/customer place. It increases the market value of the product.
3) If functional tests specify what program you should do whereas non-functional tests describe how it should behave.
4) Non-functional tests are usually automated. Dedicated tools help model-real world environments to check how the software behaves under various preset conditions.

Functional vs Non-Functional tests

Functional Tests Non-Functional Tests

1) Tests Features/Functions 1) Tests Non-functional
aspects

2) Evaluated as either present 2) Evaluated on the

or not present scale

3) Usually done manually 3) Usually automated

4) Checks the accordance to 4) Checks the
customer requirements accordance to end
user expectations
5) Tests what product does 5) Tests how product
does
6) Requirements are easy to 6) Requirements are
specify hard to specify

Functional Testing Example An online portal on which user logs in with their user account and password. The login page has two test fields for username and password. It has two functions - Login and Cancel

When successful login it goes to Home page and cancel button cancels the login.

Non-functional testing Example Upto 10000 users login at the same time and the application load time should not be more than 5 seconds.

Testing Techniques with examples

Chendur Murugan S — Mon, 05 Feb 2024 02:24:45 +0000

Boundary Value Analysis:

This is a testing technique which organisations use by evaluating data based on its boundary values or opposite ends(i.e minimums and maximums)
This helps to check software errors more efficiently and developers use this to analyse behaviour of a software program and examine its functionality.
Instead of focusing on only on centre of the data it helps to detect errors which occurs in boundary values of valid or invalid partitions.

Significance:
It reduces the test execution time
Possible to automate
It offers more control over test cases
Example:
An user needs to create an password of 4 digit number. So the boundary will be 0000 to 9999. Boundary Value testing ensures any value above 9999 is invalid and below it is valid.
Decision Table Testing:
This is a systematic approach that allows testers to evaluate various combination of inputs and conditions to ensure comprehensive test coverage at complex business setup.
Benefits:
Comprehensive test coverage
Efficient test design
Reducing redundant test cases
Traceability of testcases

Example:

Consider a loan approval system to determine a customer is eligible for a loan based on credit score, income, loan amount. A decision table is created with conditions as low, medium, high and loan approval is based on the score made using conditions we get from evaluating credit score, income, loan amount etc

Use case testing:
This is a black box functional testing used to identify test cases from the beginning to the end as per usage.
We can create a test scenario that can test the entire function from start to end.
It explains the testers how the end user uses the software at their business.

Significance:

It helps to identify the functional need of the system.
It connects the need of end user to tester
Complete analysis of the test cases and and detailed focus on each segment of the test cases at a time.

Example:

Food delivery app - here the user uses it to search the restaurant to search for the hotels and food and placing the order and does the payment after food reaches his premises. Use cases are created for each step of a process in the software.

LCSAJ Testing:
LSCAJ stands for Linear Code Sequence and Jump. It is type of white testing.
It is used to determine the code coverage under test. It begins at the start of the program and ends at the end of the program.
It is a kind of segment of code, executed in the linear sequence and followed by the control flow jump.
It has three items
Start of the segment involving executable statements in the linear sequence
End of Path
Target line to which the control flow is transferred after the end of the sequence.

Significance:

In the process of dynamic analysis testing of software application to find out the quality of the testing to be performed.
It is a test design technique, which is used to design and create test cases, effective in the executing the Linear Code Sequence and Jump in the program.

Example:
Age eligibility check for TNPSC Examination:

Program checks whether user age is under limit or not for applying TNPSC Exam.

Age = int(input())

if (Age<32):
print ("You can apply")
else:
print ("Sorry can't apply")

This program gives permissin to apply if the input value is under the limit and vice versa.

Software Testing - Things to Know

Chendur Murugan S — Sun, 28 Jan 2024 09:22:28 +0000

What is Software Testing?

Evalution of function of a software application/build to find any bug/error

Checking whether software is having all the necessary/ specified requirements given by clients/customers

Identify defects and reporting them to develop a quality application software

Finding the gaps or missing requirements against actual requirements

**_Things to know about Software Testing:

Lifecycle:_**

        Requirement Analysis
                   | 
            Test Planning
                   |
         Test case development
                   |
         Test Environment setup
                   |
             Test Execution
                   |
           Test cycle closure

Testing Types

          1) Manual Testing
          2) Automated Testing