Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (19)
Destacado
Similar a Quality Assurance Testing
Similar a Quality Assurance Testing (20)
Último
Último (20)
Quality Assurance Testing
- 2. SDLC
- 3. Testing Process Requirements Test Planning Test Case Development Test Case Execution Test results Reporting Defects Retesting Regression testing Test Closure
- 4. Types of Testing S Integration testing S Functional testing S Performance testing S Defect fix validation S User acceptance testing (aka Ad hoc testing) S Regression testing S Production testing
- 5. Requirements S Requirements can be gathered from different sources. S Examples: S Business requirement document S Design specific documents S Wireframes S Meetings S Use Cases
- 6. Test Suite S A collection of test cases that are intended to be used to test software program to show that it has some specified set of behaviors.
- 7. Test Cases • Webpage Login Feature • 1. User attempts to login with wrong credentials • 2. User logs in with right credentials • 3. User logs out • Login with wrong credentials • Login with right credentials • Logout
- 8. Test execution S Test cases are assigned to tester. S Tester executes test cases in Test Lab. S User can pass and fail test steps. S A bug is reported for failed test cases. S Bug is created in testuff S Bug is posted to desired bug tracking tool.
- 10. Is it a valid bug?
- 11. Error Management S Meetings to discuss defects, priority and fixes involving: S QA Dept. S System & Interface development S Project Management
- 12. Questions?
Notas del editor
- Aim is to prove that all areas of the system interact with each other correctly (E.g:Oetker)Assures that each element of application meets the functional business requirementsProves that the documented performance standards/requirements are being metDefects and issues raised during development cycle should be retested to validate fixesBehave as an everyday user would – interact with application/website in unexpected manners – see how actions are handledPerformed after release of each phase.Ensure that there is no impact on any previous releasesTest the application in the production environment.
- User can create test suites before writing test cases. User can start writing test cases in the relevant suite.
- User can click the settings button on home page to open Settings window. Click ‘Add bug tracker’ and select Bug Tracker tab and enter relevant information. Click Set my Lighthouse user to enter lighthouse email and password.After adding the bug tracker, click ‘Edit’ button on the right side of the project name on home page. Select Lighthouse from the bug tracker drop down menu in the project settings window.
- User can add a new lab. Click ‘Add lab’ to open ‘New Lab’ window. Enter relevant information to create the lab.