DEV Community: Rajessh Kumar Ramakrishnan

Functional and Non-functional testing

Rajessh Kumar Ramakrishnan — Fri, 10 May 2024 20:20:50 +0000

Functional testing:
Functional testing is a software testing done by both Manual and Automation to make sure the software meets the Software required document and business requirements from the customer. According to the client needs, we focus on preparing the test cases including both positive and negative cases, so that the software guarantees the clients by covering all the test cases from the start to end.
Non- functional testing:
Non-functional testing is a software testing also done by both manual and automation team to mostly check the throughput and sensitivity of how the software is performing after making sure the functionality of the software such as reliability, performance and usability. Even the OS upgrade comes under non-functional testing.
Types of functional testing:
Unit testing: Unit testing is a testing where when the developer starts to develop a new feature, they write a test case and start testing the feature to make sure it works as expected from the software requirement document.
Integration testing: Integration testing is a testing where when software is getting built, the multiple features are tested to make sure whether it’s working as expected when they are integrated.
Regression testing: Regression testing is a testing which will be done when there is a small change or any code change kicked in to make sure it doesn’t affect the software. So, when doing regression testing, the existing features should work as expected as it’s untouched.
Sanity testing: Sanity testing is a testing which is also a sub-set of regression testing which will be done once they upgrade it after all the code changes kicked in. So once the final version is available, testers do sanity testing to make sure the software works as expected.
Smoke testing: Smoke testing is a testing which done to verify the build is working as expected.
User acceptance testing: User acceptance testing is a testing done in the end as sanity testing before releasing the software.
System testing: System testing is a testing which includes both hardware and software where when the final version of the software is released and it will be done end to end testing.
Performance testing: It comes under non-functional testing where it makes sure about reliability and performance where when we load too many jobs, it doesn’t get crash or it works as expected to meet the requirements given by systems or developer.
Stress testing: Stress testing is a testing where the tester can load as many as jobs needed to check if the software can handle the jobs without crash and passes without any issues. So basically, it just checks and validates what’s the correct behavior when we load heavy jobs in the software.
Load testing: Load testing is a testing which will be done by the multiple users at a same time to validate the robustness and performance of the software.
In short, Functional testing is more focused on business requirement and non-functional testing is more focused on performance of the software.

Testing Techniques

Rajessh Kumar Ramakrishnan — Fri, 26 Apr 2024 20:33:30 +0000

Boundary Value Analysis:
Boundary Value Analysis is a software testing technique used based on boundary value set with valid and invalid partitions with maximum and minimum values. And it checks for the input values near the boundary that partitions set and gives an output whether it comes under valid or invalid and gives a user with more defects than false defects. Mainly, Boundary value analysis is used to find defects near the edges.
For instance, the job applications need to be received over 18 and under 35.
Age (1 = <17) Age (=18<35) Age (>35<60)
Invalid Valid Invalid

Decision table testing:
Decision table testing is a software testing technique is also called as Pairwise testing where we can use a combination of multiple inputs to test and find defects. Comparatively, Decision table testing covers most of the test scenarios as we combine multiple test cases and it improves the quality of the product. It’s also known as Requirement Traceability Matrix where it maps all the requirement with the test cases. It provides the document where it covers all the test cases with the combination to find errors.
For instance, Let’s take a Login account for PVR Cinemas.

Testcase 1: The registered mobile number should be correct. Hence, the user should be getting OTP to his registered mobile number.
Testcase 2: The registered mobile number was correct but the OTP was wrong. Hence, an error message should be displayed as “Please enter the correct OTP”.
Testcase 3: The registered mobile number was wrong. Hence, an error message should be displayed as “Incorrect Mobile number, please enter the registered mobile number to proceed”.
Testcase 4: The registered mobile number and OTP entered should be correct. Hence, the user should be redirected to PVR homepage.
Use-case Testing:
Use-case testing is a testing technique written by user as it’s a user-oriented and not a system oriented. The client will provide the Customer Requirement Specification and the developers will write a testcase and the clients will review it to make sure and once it’s get approved by client, the developers will start the coding. Once the application is developed, Testers will test the application. So, the Use-case testing is mainly focused by User-approach and Scenario-based testing.
LCSAJ Testing:
LCSAJ stands for Linear Code Sequence and Jump comes under a White box testing technique to identify the code coverage, from end to end which can begin at anywhere from the start or branch or end of the program. It also helps in designing new test cases, which can also increase the code coverage under the test.

Software Testing

Rajessh Kumar Ramakrishnan — Fri, 26 Apr 2024 20:31:21 +0000

Software testing is a process of testing the product or software to meet the customer requirements by making sure it has the better quality with a bug free product or software. In addition, with a bug free software/product, Software testers make sure the product is assured with efficiency, throughput and sensitivity with the advancement of the features in addition and doesn’t impact the product/software. In short, Software testers not only do the bug verification and they validate the features to make sure the product meets the SRS/MFD and satisfies the customer requirements and profits the business.
Mainly, there are two types of testing, Black box testing also known as Manual testing which is done manually who doesn’t need to know any coding knowledge and can just test by following the procedure or test case or by creating a test case by following the SRS/MFD. White box testing is also known as Automation testing where it needed coding knowledge and the coding will just follow whatever the manual testers do effectively by rerunning the test scenarios multiple times.
In the testing phase, there are multiple types of testing done such as Regression, Smoke/Sanity, Unit, Integration etc., Regression testing is a testing where any code changes or advancement with the features involved, Testers make sure it doesn’t affect the software and at the same time it works efficiently along with the features whereas Sanity testing is a subset of Regression testing which done in the final build which going to be released to the customers to make sure by doing a overall testing in a small time. Similarly, Unit testing is a testing which done for every individual features or components before assembling or making it as a software. Integration testing is a testing where we merge two features or components and check the functionality of the product/software. Once the testing is done, It need to have a proper reporting with the tool such as IBM, JIRA for the bug tracking and verification as it allows people from various teams such as Project Management/ Developers/Testers/Marketing to have a discussion to avoid such bugs and Root cause analysis. In the end, Software testers need to make sure the product/software works as expected according to the SRS/MFD and meets customer requirements with the quality standards and profits the business.

Advantages of Testing: Quality of the product/software and Customer satisfaction.
Disadvantages of Testing: Manual testing somehow can have user error or miss the bug which might cost the business but at the same time, it is better to find earlier than never.