SLIDE 1
Introduction to tactics and tools to streamline and improve your debugging process so you can squash bugs and reign joy and efficiency on your prefecture/project stakeholders.
The Project Manager as Godzilla Learn to Squash more bugs more - - PowerPoint PPT Presentation
The Project Manager as Godzilla Learn to Squash more bugs more - - PowerPoint PPT Presentation
The Project Manager as Godzilla Learn to Squash more bugs more quickly Session Goals Introduction to tactics and tools to streamline and improve your debugging process so you can squash bugs and reign joy and efficiency on your
SLIDE 2
SLIDE 3
Don’t be this:
SLIDE 4
Be this:
SLIDE 5
Tactics
Train your clients to understand why bugs exist and how to be better bug trackers. Teach them to always do the following: Provide URL Screenshot Browser and version Current behavior vs expected behavior
SLIDE 6
Tactics
Weed Out False Positives PMs should understand the difference between
- perator errors and actual ghosts in the machine
Distinguish between bugs and new features to manage scope creep
SLIDE 7
Tactics
Get to know the Drupal CMS and DEBUG on your OWN!
- Clear caches
- User mgmt (add user, resend passwords, review permissions)
- Content workflow (find authors, different content types,
publish/unpublish
- Menu changes
- Recent Log Messages (Error Report)
- Encourage peeps to not be scared of Drupal UI and gain a basic
knowledge of the structure
SLIDE 8
Tactics
Get your clients to speak in user story lingo not subjective jargon Bad: I should be able to click here and see all the recent posts Good: An unauthenticated user can view recent blog posts by selecting the “recent posts” button from the siderail Leverage Agile Methodologies Iteration/Communication/Prioritization
SLIDE 9
Tactics
Example User Story Ripe for Behat Testing: Scenario: Administrator is able to log in and create Basic Page content Given I am logged in as a user with the "Administrator" role When I visit "node/add/page" And I fill in "Title" with "[random]" And I fill in "Body" with "Test content." And I press "Save" And I visit "admin/content" And I should see "[random:1]" And I click "[random:1]" Then I should see "Test content."
SLIDE 10
Tools
- Skitch or Jing: annotated screenshots and screen
recordings
- Feedback Modules: Can connect to ticketing
systems or Jira Capture
- Spreadsheets
- Best Practice CI tools like: Travis, Probo
SLIDE 11
Tools
SLIDE 12
Q&A
What pain points have you experienced as a PM with the QA/debugging process?
- Client visibility of progress (use Kanban)
- Training clients to provide right/useful info
SLIDE 13
8 Steps to help you Squash Bugs
1. Train your clients to assist the process better 2. Manage client expectations at the outset 3. Know the difference between new feature requests and bugs 4. Be a better first responder and learn the Drupal UI 5. Take advantage of Agile methodologies and available tools 6. Draft user stories for automated testing 7. Use CI tools like Probo to conduct unit testing before merging/deploying 8. Devise your touchdown dance to celebrate a successful launch
SLIDE 14
SLIDE 15