QA engineers often tests same/similar parts of software, and if they find a bug, the information they need to collect can be predicted.
For example, for apache2 problems, following are needed:
- Attach (tarball) /etc/apache2 content
- Attach (tarball) /var/log/apache2 content
- Attach (tarball?) the page that caused the problem
Goal of this project is to write GUI app, that helps to create bugreports. The tool is meant to run on user's workstation, since it stores templates, configurations, etc. Workflow is:
- User tests on SUT (test host) and find a bug
- User on his workstation starts the application
- User enters:
- Summary (bug title)
- Description (including steps to reproduce, etc.)
- Component, product, etc.
- Assignee (with some query functionality - e.g. find by osc command from OBS, etc.)
- credentials to SUT - program initiates ssh connection to get data:
- User selects files to add
- User can also run some commands there (e.g. lspci > file)
- Order is important, so the user can first run some commands and then add their result to the bug
- User hit submit, enter bugzilla credentials, and bug is created
It is also possible to create templates: stored pre-filled forms including which data to submit and which commands to run (so the "command" must be stored, not just its output).
This way, user can just "start new bug from template" -> choose template "apache2", and the logs and configurations will be added to bugreport automatically. User than manually change it/add missing parts and submit it
User can has as many predefined templates as (s)he want.
Looking for mad skills in:
Nothing? Add some keywords!
This project is part of:
Hack Week 10
This project is one of its kind!