QualityAssuranceProcesses-GoodCoreSoft

7/31/2019 QualityAssuranceProcesses-GoodCoreSoft

1/17

Quality Assurance Processes

Presented By:

Danish Ejaz

Danyal Khan


2/17

Introduction The purpose of this presentation is to explain the QA

Processes and documentation methodology to all theteam member working in projects that includes(Project manager, Team leads, Developers and SQAs).


3/17

Requirement analysis and

gathering phase SQA should ask for a categorized requirement and

sub-requirement document from the project team. SQA should conduct meetings related to the

requirement document understanding.

Add the requirement and sub-requirement in the

requirement management tool. Manage requirement changes throughout the

development cycle.


4/17

Developers Involvement Developer should discuss the complicated

requirements with the SQA and build understanding.

Developer and the project manager should convey thechange requirement to SQA as soon as it is ask by theclient.

Developers are required to convey the details of the

meetings related to requirement change or any updatein requirements document.


5/17

Software planning Test matrix (Template Under progress) Initial draft of test plan (Template Under progress)


6/17

Developers Involvement In the software planning phase developers are required

to provide and additional requirement that is neededto a specific project.

For example:

Installing any particular software.

Updating any component


7/17

Design phase Complete the test plan Complete the test cases


8/17

Components of Test Plan Test case generation

Smoke test generation

Functional and regression testing

Integration testing

UI testing

Automated testing

Post release testing UAT testing

Release management


9/17

Bugs Reporting Bugs reporting is an important part of the testing

cycle.

Posting correct bugs with correct details reduces thefrequent communication between SQA and developer.

Explain the Bugs Reporting Guideline. Bugs Reporting Guideline
http://172.16.16.200/Software/QA_Documents/BugsReportingGuideLines/BugsReportingGuidelines-GoodCoreSoft.docxhttp://172.16.16.200/Software/QA_Documents/BugsReportingGuideLines/BugsReportingGuidelines-GoodCoreSoft.docx


10/17

UI Testing Internet Explorer 9 Internet Explorer 8

Internet Explorer 7 Firefox 12

Google Chrome

Safari Desktop

Safari IPhone

Safari IPad


11/17

Smoke Test GenerationA smoke test case document is created for the purposeof making sure that all the basic feature of theapplication is tested in every release.

Smoke test case template. Smoke Test Template
http://172.16.16.200/Software/QA_Documents/Document%20Templates/Smoke%20Test%20Template.xlsxhttp://172.16.16.200/Software/QA_Documents/Document%20Templates/Smoke%20Test%20Template.xlsx


12/17

Developers Involvement Developers are required to have the code freeze while

Smoke test is performed.

If the Smoke test is of 1 hour then developers shouldgive the internal build an hour before.

No new features should be added


13/17

Post Release TestingA post release document is prepared to make sure that

every build that is deployed on live site goes throughthe basic set of test cases.

Testing must be such that it should not effect thefunctionality on the live site

Post release testing document template. Post Release Testing Template
http://172.16.16.200/Software/QA_Documents/Document%20Templates/Post%20Release%20Testng%20Guidelines-Template.xlsxhttp://172.16.16.200/Software/QA_Documents/Document%20Templates/Post%20Release%20Testng%20Guidelines-Template.xlsx


14/17

Developers Involvement On deploying the application on the live environment

developers must make sure that every file and featureis up there.

Should be able to resolve any issue arising on the livesite.

Deployment time must be such that post releasetesting can be performed at ease and issues, if therecan be catered.


15/17

Release ManagementA document of release notes is prepared to manage the

releases for the projects and identify the known issuesand out of scope issues etc.

Explain the release notes document. Release Document Template
http://172.16.16.200/Software/QA_Documents/Document%20Templates/Release%20Notes-Template.docxhttp://172.16.16.200/Software/QA_Documents/Document%20Templates/Release%20Notes-Template.docx


16/17

Developers and PM Involvement

Developers are required to provide the latest buildinformation and the additions and changes made.

Known bugs identified should be resolved in thecoming releases.

Project managers should discuss the out of scopeissues with the clients.


17/17

Q/A

Question & Answers