| === maclin1 is now known as maclin | ||
| === maclin1 is now known as maclin | ||
| === chihchun_afk is now known as chihchun | ||
| === chihchun is now known as chihchun_afk | ||
| === chihchun_afk is now known as chihchun | ||
| === maclin1 is now known as maclin | ||
| === qwebirc159792 is now known as slickymasterWork | ||
| === bdmurray_ is now known as bdmurray | ||
| === chihchun is now known as chihchun_afk | ||
| sak | Morning QA squad | 15:47 |
|---|---|---|
| davmor2 | sak: morning | 15:54 |
| sak | If there is a bug in the testcase of an application, how do I indicate that in the bug report? There are some testcases that needs adjusting, yet the application itself seems fine. I don't want to confuse the ubunt bug-squad. | 15:54 |
| sak | Morning davmor2 | 15:54 |
| flocculant | sak - report the bug here https://bugs.launchpad.net/ubuntu-manual-tests/+filebug | 15:55 |
| flocculant | make sure that you mention the number of the testcase | 15:56 |
| flocculant | you can get that from detailed info on testcase http://iso.qa.ubuntu.com/qatracker/testcases/1655/info for example | 15:56 |
| sak | Thanks flocculant. Reading it now | 15:57 |
| flocculant | sak: the link is just a testcase - showing where the testcase ID is :) | 15:57 |
| balloons | we love to hear about testcase updates sak. Even better if you propose the fix! | 16:00 |
| sak | Another thing, its it possible to actually fix a bug? I am not a developer, so not very skilled in programming which I am guessing I have to be in order to reverse engineer a bug | 16:00 |
| flocculant | sak: a bug in a testcase is fixable for anyone who can type :) | 16:01 |
| flocculant | and read a little bit ... | 16:01 |
| sak | flocculant, what about a bug in the actual application? | 16:01 |
| flocculant | no idea :p | 16:02 |
| sak | For now, I guess I should concentrate on filling easy understandable bugs. Small steps | 16:05 |
| flocculant | sak: yep | 16:08 |
| flocculant | keep an eye on the one you report - you can propose fix for it when it gets that far :) | 16:08 |
| flocculant | people here would be more than willing to help you where needed | 16:08 |
| flocculant | you'll need to do https://wiki.ubuntu.com/QATeam/DevelopmentToolsSetup | 16:09 |
| sak | Got it flocculant | 16:11 |
| flocculant | then you can look at https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual/Writing | 16:12 |
| flocculant | obviously you're not writing one - but most of the steps are the same at the beginning :) | 16:12 |
| sak | flocculant, I have written one in the past that successfully got merged. Though, a little review won't hurt | 17:19 |
| flocculant | aah - then you know what to do - only different bit is reporting it and waiting for confirmation :) | 17:21 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!