1 / 11

7 tips to have software tested without specification

The launch of “time-to-market” product is often bound with time pressure, that causes lack of specification and requirements. No doubt, that product quality should be verified. But it doesn’t mean that you have to postpone the product launch to elaborate the documents. Following simple tips and cooperating tightly with your testing team or provider, you will have your software tested, even if you have minimal software specification, no testing requirements and lack of time and specialists to elaborate them

qatestlab
Download Presentation

7 tips to have software tested without specification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 7 tips to have software tested without specification Dana Zhezdrina QATestLab Program Manager

  2. 2 About me 7-year experience in testing 3-year experience in program management Finished Executive Development Program "Project management for creative teams. Agile in actions" in kmbs Don't like bags and fond of dogs © QATestLab. All rights reserved.

  3. 3 For time-to-market software that invokes much pressure, documentation creation is omitted to save time. But testing is still to be conducted. How to have the product tested with no or minimal specification? © QATestLab. All rights reserved.

  4. 4 Tip 1 Supply QA team with general information about the project. To clear understand the product specifics, let someone form the team make a quick demo. © QATestLab. All rights reserved.

  5. 5 Tip 2 Provide QA team with all available documentation: • written requirements • backlog • user stories / use cases • mockups • help cases • FAQ • etc. © QATestLab. All rights reserved.

  6. 6 Tip 3 User testing, performed by specialists unfamiliar with the product, detects the issues with user acceptability of the system. © QATestLab. All rights reserved.

  7. 7 Tip 4 The risk-based testing can be started from the most critical and high-use features and ones to be released soon. © QATestLab. All rights reserved.

  8. 8 Tip 5 Test documentation including test cases and checklists ensures proper understanding of selected approach. © QATestLab. All rights reserved.

  9. 9 Tip 6 Review and confirm the received test results. © QATestLab. All rights reserved.

  10. 10 Tip 7 Ensure continuous learning of QA team by sharing product data and usage analytics, user information, further plans and product visions. © QATestLab. All rights reserved.

  11. 11 Thanks

More Related