Welcome back again on this lovely Thursday!
We have covered Phase 1 and 2 of an Application Lifecycle and now we are on Phase 3.
Quick Overview So Far:
Phase 1 covers planning which is where specifications (requirements) are gathered from the customer(owner) of the project so that everyone knows EXACTLY what is taking place. Phase 2 is where all hands (marketing, sales, support, developers, testers, etc.) are brought together to review the specifications and tie together a process of what will take place to get the project done. During this time, testers would also formulate what needs to be tested.
During Phase 3 of this process is Testing (which is the most important stage!). There are four components of testing that take place during this stage: Unit, Integration, System and Acceptance testing. Below you will find each component of testing broken down with some help from Segue Technologies(I really loved the way they define their testing definitions):
During this first round of testing, the program is submitted to assessments that focus on specific units or components of the software to determine whether each one is fully functional. The main aim of this endeavor is to determine whether the application functions as designed. One of the biggest benefits of this testing phase is that it can be run every time a piece of code is changed, allowing issues to be resolved as quickly as possible. It’s quite common for software developers to perform unit tests before delivering software to testers for formal testing.
Integration testing allows individuals the opportunity to combine all of the units within a program and test them as a group. Keep in mind that no matter how efficiently each unit is running, if they aren’t properly integrated, it will affect the functionality of the software program.
System testing is the first level in which the complete application is tested as a whole. The goal at this level is to evaluate whether the system has complied with all of the outlined requirements and to see that it meets Quality Standards. System testing is undertaken by independent testers who haven’t played a role in developing the program. This testing is performed in an environment that closely mirrors production. System Testing is very important because it verifies that the application meets the technical, functional, and business requirements that were set by the customer.
The final level, Acceptance testing (or User Acceptance Testing), is conducted to determine whether the system is ready for release. During this final phase, the user will test the system to find out whether the application meets their business’ needs. Once this process has been completed and the software has passed, the program will then be delivered to production.
The method of deliver from testing to production is called Implementation which we will discuss next week! One part of testing that is also done, but wasn’t mentioned is Regression Testing(SmartBear). I didn’t feel the need to list that as a single component of testing because it can take place within Unit, Integration, System and Acceptance testing.
Testing as a whole is a vital and very curial part in the process with in ALM.
If you haven’t already, please take the time to follow me on FB (Charizma Jones), IG (charizmajones) or Twitter (@CaptureMe_TPPB) that we can have further discussion on my articles or so I can hear your perspective on things! You can also email me at SJ.TheProfessionalProjectBlog@gmail.com
That’s all for now!!!! Enjoy the rest of your week and see what Friday Funny or Financial Friday tips may be coming your way from BNEW