https://bugs.documentfoundation.org/show_bug.cgi?id=133193
Bug ID: 133193
Summary: QA bugs nuances
Product: QA Tools
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: General
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: james.adams.5...@gmail.com
I was amazed at the question and, most importantly, quite disappointed that I
was unable to find an excellent answer.
But it made me think. And that prompted me to research and exchange ideas with
others in the bug reporting world.
And today I am happy and ready to answer this question. Here
https://www.wowessays.com/ are the most important bug reporting skills you
need.
Knowledge, workflows and skills.
Reporting and tracking bugs requires a specific set of skills that are quite
different from those required in other areas such as design or development.
Over the years, we have learned a lot about the excellent workflows, tools and
bug reporting frameworks, but few have addressed the issue of bug reporting
skills.
The reason why quality control requires a particular type of profile is that it
is the only part that is in the middle of the software development matrix, in
collaboration with and between developers, designers, product managers, users
and customers.
If you think about the role of quality control and bug reporting, you can think
of an intermediary. The intermediary is the one who is in contact with the
alpha and beta testers and the customers. The people in QA and in test are
those who have to tell the web developer to change (correct) their code.
And when the situation demands, they are also the ones who tell web designers
that their design is not intuitive enough for end users.
bug reporting skills for qa agents
They communicate with the product team and make sure they are on the right
track to fix existing bugs. All of these people have different programs and it
is up to the quality assurance officer to make sure everyone is aligned and
knows what needs to be done.
Quality assurance officers, testers, or bug reporters (whatever you call them)
must speak more than one language. They basically need to understand how the
whole product works (to some extent).
So what are the great bug reporting skills you should have?
1. You must have great technological skills
bug reporting skills like Sherlock Holmes As a tester, you are hired to support
certain software or products. You are the one who follows every little step,
every little clue. You are tracking bugs. You are Sherlock Holmes.
It really takes great technology and development skills to find bugs, document
them, and provide a full description of how to make them reproducible. You
should at least be a little familiar with the different programming languages
used to develop the product and with the basic configuration of the systems
used.
I'm not saying you have to be a developer genius, certainly not. But you must
have a basic understanding of front-end and back-end technologies. You need
this understanding to be able to speak with the developers responsible for
solving the problems you have discovered.
2. You must be good at communication
So much money has been and continues to be lost due to miscommunication.
It is so easy to guide a development team in the wrong direction by simply
having a terminology mismatch or mismanagement of expectations.
That said, when a quality assurance agent or tester finally has information, he
should be willing to ask questions of the developers when questions need to be
asked.
Managing ambiguity is essential.
Otherwise, you will have entire teams going on a wild geese hunt, trying to
identify or recreate a bug.
It also means that a good quality assurance officer doesn't care about reaching
out to people and engaging in open conversation.
3. You must be a diplomat
It is always difficult to find and highlight the mistakes of others using
https://www.google.com/. Doing this as a tester or bug reporter means that you
need to be able to work with these people effectively. It also means being able
to get the job done even if it means having to deal with a little resistance
and cranking here and there.
Nobody likes bugs and nobody likes to find them. Establishing a culture of
open-mindedness of trial and error is absolutely essential here.
It doesn't help point the finger at your developers for certain bugs or errors.
It just doesn't work.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
