3 Main Methods of Debugging an Application

1
3 Main Methods of Debugging an Application
Office in Ukraine Phone 380 (472)
5-61-6-51 E-mail contact (at) qa-testlab.com Addr
ess 154a, Borschagivska str., Kiev,
Ukraine http//qatestlab.com/
2
3 Main Methods of Debugging an Application
When the development of an application is in
process, it is ok that the system has many
defects. Software bugs appear all the time,
especially during smoke testing, new feature
testing, functional testing, unit testing
or integration testing. When software bugs are
found, it is necessary to determine their nature
and the reason of their appearance. It is better
to do it without making changes in the system
under test. For this purpose the project should
operate in several modes.
Office in Ukraine Phone 380 (472)
5-61-6-51 E-mail contact (at) qa-testlab.com Addr
ess 154a, Borschagivska str., Kiev,
Ukraine http//qatestlab.com/
3
3 Main Methods of Debugging an Application
As a Rule, a Project Operates in 2 Modes
Debug mode
Release mode
It allows software testing company and
development team to determine causes of the
discovered errors appearance.
In this mode a project goes in production, there
are no debugging-related elements in this version
of an application.
Office in Ukraine Phone 380 (472)
5-61-6-51 E-mail contact (at) qa-testlab.com Addr
ess 154a, Borschagivska str., Kiev,
Ukraine http//qatestlab.com/
4
3 Main Methods of Debugging an Application
There Are 3 Main Methods of Fixing Errors in an
Application
real-time fixing
code examination
using defect recording mechanism or defect
reports.
Office in Ukraine Phone 380 (472)
5-61-6-51 E-mail contact (at) qa-testlab.com Addr
ess 154a, Borschagivska str., Kiev,
Ukraine http//qatestlab.com/
5
3 Main Methods of Debugging an Application
Real-Time Fixing
Code Examination
During this kind of fixing errors a tester uses
debugging program that helps to inspect the
system code when the discovered errors are being
reproduced.
If a software bug is not very complicated it is
possible to find out its cause by visual
examination of the source code.
Using Defect Recording Mechanism or Defect Reports
If records are kept during mobile testing,
desktop testing or web site testing, or there is
detailed defect description, the developer can
execute steps to reproduce the defect and
discover the cause of the problem in the source
code.
Office in Ukraine Phone 380 (472)
5-61-6-51 E-mail contact (at) qa-testlab.com Addr
ess 154a, Borschagivska str., Kiev,
Ukraine http//qatestlab.com/
6
Thank you!
Office in Ukraine Phone 380 (472)
5-61-6-51 E-mail contact (at) qa-testlab.com Addr
ess 154a, Borschagivska str., Kiev,
Ukraine http//qatestlab.com/