I talk to development teams about bugs from the user’s perspective rather than a developer’s. In my role, I put myself in the user’s shoes in a way that’s hard for a developer that’s too close to the project.
#GHOSTLAB FOR WINDOWS HOW TO#
I sometimes sit down with the team, or we bounce ideas off each other on how to make a feature better.
I want the bug fixed just as much as they want to fix it. I try to be as concise as possible (no developer wants to have to read paragraphs of text to figure out what the problem is!) Basically, I try to be as helpful as I can be in answering any questions they have or helping them track down where the issue is occurring. If I find an issue, I will submit a ticket that contains all the relevant information for the developer to reproduce and debug it.
Then in the afternoon, I usually follow the testing plan- cross browser, cross device testing.īut no two days are ever the same in an Agile environment, and it’s never boring! How do you highlight potential bugs and issues for the development team? There’s a pass/fail for each test matrix field, or each device to each browser. This test case would go into a test matrix that contains intersections of all devices and browsers. A test case, for example, could be that the close button on the popup needs to highlight when a mouse hovers over it. I write the test cases, or reproducible steps to test a feature, in the morning.
I have a testing plan that adds on only whatever stories or group of tasks the teams are working on in that sprint. In a typical day, I attend all the scrum meetings in the morning for the teams I’m working with. And we’re involved from every step on a project from the very first sprint, to development, and release. We’re involved in estimates before a contract is signed.
#GHOSTLAB FOR WINDOWS SOFTWARE#
When does QA play a role in software development?Īt Caktus, QA is involved from the beginning. QA will make sure that the user is getting the best experience possible. Things don’t always line up between design intentions and technical implementation, and we have to be able to call out anything that doesn’t make sense. We have to think about whether the application feels good, feels enjoyable for users. Whatever they or the organization has set as their quality threshold, QA ensures that is being met. We hold the development team to their own definition of quality. QA for a web project means testing across selected devices and browsers to make sure the site works as intended. It’s part of a natural impetus to create order out of chaos.
So I continued into software QA after that. I was doing language quality assurance testing, testing translations in social games. Charlotte Fouque, Caktus’ QA Analyst, sheds light onto what exactly quality assurance is and the intricacies of doing it well. The craft and expertise behind the work of QA professionals, as a result, can sometimes feel hidden. Because quality assurance (QA) is all about creating a seamless application experience across any number of devices, it’s most successful when no one notices it.
0 kommentar(er)
