|
|
| (3 intermediate revisions by 2 users not shown) |
| Line 47: |
Line 47: |
| | <!--Sub Header End--> | | <!--Sub Header End--> |
| | | | |
| − | <br>
| + | {| style="background-color:white; text-transform: uppercase; font-size:14px; font-weight: bold; text-align:center; padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" | |
| | | | |
| − | [[File:Testing_pyramid.JPG|700px|center]]
| + | | style="vertical-align:top;width: 25%;" | <div style=" padding: 3px;line-height: wrap_content; border- bottom: 5px solid #000000; font- family: helvetica"> [[SMT483G2: Cerebro User Testing| < font color =#272d2d>< b> Internal Testing< /b></ font> ]] |
| − | ==Testing Procedure==
| |
| − | <div style="font-family: Garamond; font-size:16px"> | |
| − | <p> | |
| − | Quality Assurance (QA) is responsible for the execution of the test plan in every sprint which will be perform by regression testing on the staging server and run tests against all test cases that have been created thus far. This helps to ensure that existing functionalities in the application are not affected by the integration and allow us to deliver an optimal product to our client.
| |
| − | </p> | |
| − | <p> | |
| − | Our test cases can be found on our private repository [ here].
| |
| − | </p> | |
| | | | |
| − | '''Testing Lifecycle''':
| + | | style="vertical-align:top;width:25%;" | <div style="padding: 3px; line-height: wrap_content; border-bottom:1px dashed #000000; font-family:helvetica"> [[SMT483G2: Cerebro User Testing Stakeholders |<font color =#272d2d><b>User Testing</b></font>]] |
| | | | |
| − | 1. Development Phase
| + | | style="vertical-align:top;width:25%;" | <div style="padding: 3px; line-height: wrap_content; border-bottom:1px dashed #000000; font-family:helvetica"> [[SMT483G2: Cerebro User Testing 2|<font color =#272d2d><b>User Testing 2</b></font>]] |
| | | | |
| − | :Every individual developer conducts local testing as they develop, on the functionalities they are assigned. Concurrently, QA constructs test cases for all functions being developed in the currently sprint, to stress test the product.
| + | |} |
| | | | |
| − | 2. Initial Testing
| + | <br> |
| − | | |
| − | :QA works alongside the respective developers to test the functions against the test cases. All bugs found are recorded into the Bug Log document. Respective developers debug the functions which they are assigned, starting from the most severe bugs. Quality Assurance verifies, through testing against test cases again, that known bugs have been resolved.
| |
| − | | |
| − | 3. Staging Server
| |
| − | | |
| − | :After all known bugs are resolved, application is hosted on staging server for regression testing. QA carries out regression testing against all past test cases. Like before, all bugs found in this stage is also logged onto the Bug Log document. Respective developers debug known bugs and QA verifies.
| |
| − | | |
| − | 4. Production Server
| |
| − | | |
| − | :After all known bugs are resolved, software implementation is pushed to production server, where Quality Assurance conducts last round of regression testing. All bugs found are documented and worked on by respective developers like before. After so, testing documentation is finalized and uploaded to wiki.
| |
| | | | |
| − | :Should there be deviations and delay in debugging, QA will report and discuss with Project Manager with regards to development cycle, and severity of the bug. If the bug is major, Project Manager will decide to halt all oncoming development work, till another round of debugging and testing is done. Minor bugs can be covered, and debugged during the next debugging session of the following sprint. | + | [[File:Testing.png|1000px|center|testing]] |
| | | | |
| | <!--/Content--> | | <!--/Content--> |
