Bugs (34)

Bugs (34)

1. UX Bugs (2)

   • Lack of resources
     • Get Jue to review reqs for UI stories
     • CC Jue in UX bugs
     • Find out UX bug triage process
     • Tag UX needs

2. Unimportant Bugs (0)

3. New Requirement "Bugs" (0)

4. S.E.P. Bugs (3)

   • Change of process and tools
     • Check ENG bug notifications for early investigation
     • TV screen displaying bugs
   • S.E.
     • Better component test coverage
     • Need integration tests

5. Genuine Bugs (7)

   • Young team
     • Collaboration between old and new team members
   • QA Resources
   • Exhaustive Manual testing

6. Cross-Browser Bugs (1)

   • Too many browser to support
     • Reduce supported browser
     • Use browserstack
     • Offloading browser testing (speak with Steve)
     • Automated tests

7. Testing Bugs (4)

   • Lack of planning
     • Better test plan
   • Lack of maintenance
     • Keep tests up to date

8. Bugs we don't have means to capture... (2)

   • ...because we don't have the hardware
     • Access to more test environment earlier
   • ...because we don't have load
     • Test under load
   • Performance test environment

9. 95% Bug fix (missing bits become new bugs) (1)

   • Missed tests
     • More tests
   • • Take investigation more seriously

10. Invalid Bugs (5)

    • Bad Triaging
      • Training in triage
    • Lack of understanding from testers
      • Reporting bugs properly
      • Get SI testers to Demo (talk to Head of QA)
      • Functional findable documentation

11. Rollout Bugs (1)

    • Deprioritizing
      • Prioritizing

12. UI Bugs Regression (5)

    • Lack of automated tests

13. Documentation Bugs (2)

    • Lack of reviewing
      • Doc review process
    • Lack of QA conversation with doc team
      • Read all doc from Badger and Doc teams
    • Bad Doc impact page

14. Splunk "features" (1)

    • System complexity

Images and files in the map