Uploaded byAndrii Dzynia
Working Software Over Comprehensive Documentation
This document provides information on various tools that can be used for agile software development and testing. It discusses tools for user stories, project planning, documentation, testing, reports, and session-based test management. Various options are presented for each category such as Excel, JIRA, Confluence, and specialized agile tools.
More Related Content
Similar to Working Software Over Comprehensive Documentation
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Working Software Over Comprehensive Documentation
- 1. "Working software over comprehensivedocumentation" ©
- 2. Andrii Dzynia Test Engineer/Consultant/Trainer @adzynia http://adzynia.com
- 3. Start of anyproject
- 5. What to use? А1paper Microsoft Visio leancanvas.com
- 6.
- 7. What to use? Paperfor WIKI flipchart Google Docs
- 8.
- 9.
- 10.
- 11. Functionality Matrix Functional Block 1 Feature Feature Feature Feature Feature 1 2 3 4 5 User Story 1 X User Story 2 X Epic 1 User Story 3 X User Story 4 X Epic 2 User Story 5 X X
- 12. What to use? MSExcel Google Docs Web System Board
- 13. Web Systems • Agilo • Scrumy • Trac • Kanban Flow • JIRA • ScramDo • Traget Process • Pivotal • Rally • VersionOne • Trello http://www.userstories.com/products
- 14. Sprint Planning In Progress Code Review Testing Demo User Task Story Task Task Team Flow http://www.adzynia.com/p/matherials.html
- 15.
- 16. For Business Requirements Plans User’s Manuals
- 17. For Developers Product Development Architecture Environment setup JavaDoc API Business Logic
- 18. For Testers Test Strategy Freedom Functional Map Business Logic
- 19. Test Strategy http://www.developsense.com/presentations/2009-10-RapidIntroToRapidTesting.pdf http://www.satisfice.com/presentations/strategy.pdf
- 20.
- 21. What to use? UMLdiagram Mind Map Checklist Matrix
- 22. Live Documentation •Systembehavior •Testing Documentation •Users’ Manual Acceptance Scenarios
- 23. Gherkin Given a ScrumMaster wants to add new user story to product backlog When adding new user story into product backlog with data | storyName | storyDescription | | US-309 Create new user | Description-Test | | US-310 Edit user | Full Description | Then system should show “User Story added” message http://www.adzynia.com/p/matherials.html
- 24. Java Code @Given(“^a ScrumMaster wants to add new user story to product backlog$”) public void aScrumMasterWantsToAddUserStory() @When(“^adding new user story into product backlog with name ”(.*)” and description ”(.*)” $”) public void addNewUserStoryIntoProductBacklog(List<String> list) @When(“^adding new user story into product backlog with data”) public void addNewUserStoryIntoProductBacklog(List<UserStory> list) @Then(“^system should show ”(.*)” message”) public void systemShouldShowMessage(String message)
- 25. Reports http://www.thucydides.info/
- 26. Reports http://xpinjection.com/resources/
- 27.
- 28.
- 29. Session Based TestManagement Charter Charters List Reports Debrief http://www.satisfice.com/sbtm/ http://pragprog.com/book/ehxta/explore-it http://www.satisfice.com/articles/sbtm.pdf
- 30. What to use? Excel Task Trackers spreadsheet Special Tools
- 31. SBTM Tools Atlassian Bonfire QA Symphony BB Test Assistant Telerik Test Studio Test Explorer Session-Based Tester Session Tester SMTB by J.B. Rapid Reporter Session Web
- 32. Automate Reporting Automatic Release Notes Metrics Automatic Charts
- 33. KISS Keep It StupidSimple Keep It Short and Simple Keep It Simple Sir Keep It Super Simple Keep It Simple and Straightforward http://en.wikipedia.org/wiki/KISS_principle
- 35.