So to start, diving into functional and non-functional testing. In the realms of software testing, we have functional testing, which you all may be familiar with, with unit testing, integration testing, smoke testing, and user acceptance testing.
So functional testing is really going to be testing the functionality of your application, ensuring that your application is meeting business requirements that were first set up and established in planning periods. And once again wanting to just ensure that your application is working as expected. And you can do just that with functional testing.
Further, we have nonfunctional testing. So this is going to be testing not around the realms of functionality and working as expected, but more of getting metrics and insight into your application, your mobile application. So for nonfunctional testing, we have load testing.
So really trying to load as many, say, users on your application to see how it performs with an influx of loading your application performance testing.
So how well your application is performing, especially performing on our real device. Usability testing or accessibility testing. So making sure that your application is being able used by all users, even with users with any disabilities or visual impairments as well as volume testing. So really ensuring that your application can uphold to an influx of servers or users on your application. As well as scalability testing.
With that, we might all be familiar with maintenance testing more commonly known as regression testing. So when we have all testing in place. We have all testing in place, we want to ensure that any new code within the cycle of DevOps, any new code within that life software developer lifecycle did not impact any existing code.
So we want to test all functional testing and non-functional testing with regression and maintenance testing.
Comments are closed.