Yes, Software Testing is an important phase of the Software Development Life Cycle (SDLC).
- Companies are expecting shorter release cycles to deliver new functionalities.
- Provide stable and bug-free products to the customers.
- Meet the expectations of customers by delivering the feature in short intervals.
- Following the Agile development, we need to fix the issues at the earliest.
- Make a fool proof system.
- Shift left model (Testing should begin at the very early stage of SDLC).
(Note: Social Media platform examples will be used for explaining.)
You download a social media application and try to “Sign Up” and an “Error” message shows up. Because of that same problem, none of the users could “Sign Up” and use the application. Now they have already started losing their business as users cannot use the application and are facing the unresolved issue at the very start. Thus, users will go and find another similar application that works and probably will never return to the previous one because of the bad experience they had.
A simple login test would have checked the system, database, and server avoiding such issues.
(Assuming firstname.lastname@example.org user exist)
The purpose of Unit Testing is to validate that each unit of the software code performs as expected. It is performed during the development phase of an application by the developers. Unit Test isolates a section of code and verifies its correctness.
- Once a login component/ module is developed.
- Write all the test cases, regression tests which will validate the correctness of the module.
The purpose of Integration Testing is to combine individual units and test them as a group. It is performed to expose faults in the interaction between the integrated units. For example, it can be testing the interaction with the database or making sure that microservices work together as expected.
- Once a news feed component is developed.
- We will need to integrate it with Login as after login users will immediately land here.
- Testing of the integrated components and their interdependency should be checked so that it doesn’t break the code.
Functional Tests are used to validate the software system against functional requirements. The purpose of Functional Testing is to check the output of the system and not the intermediate states. The test would expect to get a specific value from the database as defined by the product requirements.
- Once a search component is developed.
- We will type some characters in the search box.
- The result of fetched should be relevant to the text searched.
End-to-end testing replicates a user behavior to test whether the flow of an application right from start to finish is behaving as expected. The purpose of performing end-to-end tests is to identify system dependencies and to ensure that data integrity is maintained between various system components and systems.
The entire application is tested for functionalities such as communicating with the other systems, interfaces, databases, networks, and other applications.
- This will cover all the pages, features, and functionality.
- This should be performed before the code is pushed to the next stage, all the test cases have to be successful.
Compatibility Testing is performed to assure that the web application is capable of running on different hardware, operating system, network environments. We need to test if the application is able to function properly in different types of browsers.
- This testing will help us know that the application is working stable across all different operating systems and browsers.
A load test enables you to measure response times, throughput rates, resource-utilization levels and to identify your application’s breaking point, assuming that the breaking point occurs below the peak load condition.
- Once the application is developed, it is necessary to know about the peak load condition the application can handle.
- Therefore, load testing should be performed to know about the application’s threshold value.
|Parameter||Manual Testing||Automated Testing|
|Accuracy||Manual Testing may not be accurate always.||Automated Testing is highly accurate as compared to manual testing.|
|Testing Time||Manual Testing is time consuming as the tester has to check everything manually.||Automated testing is faster as it operates on tools.|
|Reliability||Manual Testing is not very reliable, because of the human factor involved in it.||Automated testing is comparatively more reliable.|
|Regression Testing||Very time consuming & complicated process to do it manually.||Much easier with the help of tools.|
|Budget||Less expensive if considered for one time or short time goal.||Expensive as it requires tools yet reasonable for long term.|
- Selenium is an open-source automated testing framework. It not only supports test scripts written in any user-preferred languages such as C#, Java, Perl, PHP, Python, and Ruby but also supports test case execution on multiple operating systems such as Windows, Linux, Android, and Mac.
- Selenium provides high testing flexibility to write advanced and complex test cases and allows tests to be carried out using any browser: Mozilla Firefox, Internet Explorer, Google Chrome, Safari, or Opera.
- Selenium can be integrated with TestNG and JUnit to generate test reports and manage test cases and with Jenkins, Docker, and Maven to attain continuous testing.
- Selenium has extensive features unlike other tools for example it provides cross-browser testing.
- The purpose of testing is to compare the actual and expected output as well as the position of the elements in the UI.
- This will also make us validate that other parts of the system like API, DB, Network, etc, are responding correctly.
- Hence, Selenium can be used to perform different types of testing. Therefore, it removes the manual dependency of testers and the developers. So that they can run the script and validate all the steps themselves. This brings everything under one roof and makes it the most preferred and used tool for testing automation.
Without reporting, all the hard work that you put into writing and executing your test cases will be lost if there’s no way to track the information and communicate it with others in your team. Selenium doesn’t support report generation, but it’s easy enough to do with the right tools. Few reporting tools that can be used along with selenium are:
- Selenium TestNG Report Generation
- Selenium JUnit Report Generation
- Selenium Extent Reports
Apart from the reporting tools, email can be sent using an API call or slack notifications.
Application testing should not only run before releasing a new feature but also it should run daily, within a period of 24 hours or 12 hours, depending on the organization.
We should make our test cycle so flexible that we can split the tests into:
A Login test should run more frequently. Like after every 5 minutes or maximum up to an hour, as it's the most critical part of an application.
Covers all different aspects of testing, edge cases, and functionality tests. This can run every day/ once every 3 days/ once every 7 days or as per the business requirements.
Only specific feature’s testing along with its dependencies are performed when needed.
Referring to the above shift, now we have more time to resolve the discovered defects. That means if the tests are performed more often, we can find the defects sooner, thereby providing us more time to fix it. Thus, ensuring a smooth experience for the customers.
Therefore, it is advised to perform early and frequent tests. This can be achieved if we configure our code to work in such a manner and make the test cases parameter driven.
Today companies are looking for developers who can take part in software development and at the same time, handle testing of the developed software, these developers are known as SDET engineers.
- To speed up the process, automation is required. This is known as DevOps.
- Automation can save time, remove assumptions, and do wide test covers.
- Manual testing has to be shifted to automated testing.
- Automation can remove dependencies.
- Selenium should be used for automation because it covers the maximum test cases.
You can read the original blog source from: blogs.nimritee.com