The Significance Of Smoke Testing In Software Development And Testing Process
Present-day application development and testing are a complex sophisticated process, demanding careful planning, much time and labor contribution. Many techniques, methods, procedures and appurtenances were elaborated in order to streamline this process. Automation of software builds compilation, smoke testing and regression testing are among them.
A new build is usually created ones a day. The process of automated build creation is often set up at the end of a working day and a new build is ready in the next morning. Automated build creation does not require human assistance if everything goes as it should.
If something goes wrong the process stops and the messages informing about the problems are sent to the responsible people. It is very important to eliminate the errors as soon as possible and to proceed the compilation. When the defects are corrected, the process restarts from the relevant place.
Such Automated Creation of Builds Often Involves 3 Procedures:
1. Compilation of an application build.
Compilation of a software new build is complex, time and labor consuming process. That is why it is in most cases automated and is performed after office hours.
2. Smoke testing of the created build.
Smoke testing is a compact variation of regression testing. It is aimed on checking the most important and the most frequently used functions of the system.
To elaborate the tests it is necessary to determine what operations of the system are the most significant.
To Such Functions Usually Belong:
- function of logging into the system;
- functions of data managing, in particular data recording, storing, processing and deleting;
- functions responsible for access to all the screens and menu selections.
Smoke Testing Is Usually Performed After:
- compilation of the application build;
- unit testing of the build;
- integration testing of the build.
Smoke testing is considered to be the first stage of any mobile testing, desktop testing or web site testing. If the results of the tests are satisfactory, other testing activities can be done. Otherwise the software must be corrected and tested again.
This process is often automated and included into the process of a new build creation. In this case a software testing company may be sure that the number of possible software bugs in the application is significantly diminished, the main functions of the application are operational and the application code is checked.
Smoke testing should be automated or it will demand much time and efforts and will make web site testing, desktop testing or mobile application testing unprofitable.
3. Regression Testing of the Build.
Regression testing of a software build is usually executed after smoke testing and included into the process of automated creation of application builds. It is usually focused on application deeper levels and logic and mostly checks the system code.
A new build is usually created ones a day. The process of automated build creation is often set up at the end of a working day and a new build is ready in the next morning. Automated build creation does not require human assistance if everything goes as it should.
If something goes wrong the process stops and the messages informing about the problems are sent to the responsible people. It is very important to eliminate the errors as soon as possible and to proceed the compilation. When the defects are corrected, the process restarts from the relevant place.
Such Automated Creation of Builds Often Involves 3 Procedures:
1. Compilation of an application build.
Compilation of a software new build is complex, time and labor consuming process. That is why it is in most cases automated and is performed after office hours.
2. Smoke testing of the created build.
Smoke testing is a compact variation of regression testing. It is aimed on checking the most important and the most frequently used functions of the system.
To elaborate the tests it is necessary to determine what operations of the system are the most significant.
To Such Functions Usually Belong:
- function of logging into the system;
- functions of data managing, in particular data recording, storing, processing and deleting;
- functions responsible for access to all the screens and menu selections.
Smoke Testing Is Usually Performed After:
- compilation of the application build;
- unit testing of the build;
- integration testing of the build.
Smoke testing is considered to be the first stage of any mobile testing, desktop testing or web site testing. If the results of the tests are satisfactory, other testing activities can be done. Otherwise the software must be corrected and tested again.
This process is often automated and included into the process of a new build creation. In this case a software testing company may be sure that the number of possible software bugs in the application is significantly diminished, the main functions of the application are operational and the application code is checked.
Smoke testing should be automated or it will demand much time and efforts and will make web site testing, desktop testing or mobile application testing unprofitable.
3. Regression Testing of the Build.
Regression testing of a software build is usually executed after smoke testing and included into the process of automated creation of application builds. It is usually focused on application deeper levels and logic and mostly checks the system code.
