Bug Life Cycle

1) Tester ----new----Test Lead----open----Development Lead ----Developer-----Fixed----Tester
Tester----re-open----Developer

When a tester finds a defect he assigns a new status for the defect and passes it to the test lead.

The test lead  verifies the defect and assigns a open status and passes it to the development lead.


The development lead then  verifies the bug and assigns it the developer.

After that the developer works on the defect fixes it and assigns it back to the tester with a fixed status.

After the tester test to see if the defect still exist. If it doesn't exist the status has been changed to closed.

However, if it still exist then tester reopens the case and sends it back to the developer.

Restesting VS Regression Testing

Regression Testing
check whether the bug or defect has not impacted the existing application

Retesting
Verify the bug or defect itself.

When does the QA come into the Project

QA needs to work from the beginning of project. This will make sure that the customers expectations are met for the quality standards.The  QA also communicates between the major teams to ensure a good test environment is set up.

Difference Between Builds, Release & Version

Build - Application is still in testing phase.

Release- Application is ready for the client.
Updates are done in the same module with o some change in requirements.

Version-  Its a whole new module

3 Quality Assurance Requirments

To Test
1) Completeness
2) Feasiblity
3) if its testable

Different Types of Application

1) Desktop Application
Microsoft word, any desktop application

2) Client Server Application
client request service from the server
OS on the client gathers information from the Server.

3) Web Server Application
Web Browser relies on the Web Server for information

4) Web Application
Cibc.com


5) Mobile Application

6) Cloud Virtual Server Application
On a Cloud server, always online.

Different Types of Software Testing

Different Types of Testing

Functional Testing
To test if commands are functioning the way they are supposed to function
ie. Valid Data & Invalid Data

GUI Testing
Graphical User Interface Testing
To test if the GUI meets the requirements in areas such as font, color, size, alignment and other properties

Smoke Testing
Set of test cases executed confirm if an application is ready for further testing

Database Testing - To test the quality of data in which the following are checked
a) Completeness
b) Accuracy
c) Duplication
d) Stored in proper location

AD-HOC Testing 
To test the application without any formal documentation.

Regression Testing
Set of test cases executed to confirm if  the new changes has not impacted the existing application.

Integrity TestingTesting of two or more module  to ensure they are working together.

Browser Testing
To test the compatibility of different browsers with applications