New answers tagged

1

If you was under the threat to lose your job as a result of letting a single bug to slip to PROD, you should consider looking for a job in saner company. It is just a matter of time when another bug will slip to PROD. Quality is a team sport. Bugs will always slip, and pointing fingers and assigning blame does NOT improve quality. Firing you for a bug is ...


6

There will always be bugs that get past a tester and land in production. I have even had bugs that where in my face, we researched it, thought it was a fluke, because we couldn't reproduce it and then released the issue into production. The best thing you can do is learn from it and prevent the same in the future. I write an automated test-case for each ...


2

First and foremost, analyse how the bug got past you. Find a way of preventing this, and things like it from happening ever again. Second and maybe even more important, talk. Talk with everyone involved with getting new functionality out. As soon as requirements materialize, get your test approach on paper and scrutinize it AS A TEAM. That a harmful bug got ...


1

Do you guys have a specific person that does Automation? If not, I would highly suggest you begin looking into Selenium since you guys are webapp-based, depending on your comfort level with coding you could start with just using the Selenium IDE and using the record function and move up to Selenium Webdriver from there.


2

Suggestions: Work on your writing and communication. You've asked two questions in your post, but haven't used question marks. Ellipses have three periods. Learn the difference between its and it's. Use an active voice in your writing. Speak to people more than you email or message. Conversely, don't socialize too much or waste other people's time. Find ...


1

qa_test235, I noticed that your are an unregistered user of this forum and I am not sure how this affects your ability to participate. Become a registered member of Stack Exchange and participate as you can in helping others learn about SW testing and quality engineering. This activity may seem unnecessary or maybe a burden. Over time this will add some ...


1

Test automation and push toward continuous delivery is slowly but surely reducing the need for manual testing. Learn BDD and other means of how to ensure developers' are writing good automated test and satisfying business needs. To go even further, learn how to write test code yourself; QA experience and knowing how to code will make you stand out from those ...


2

Are you recommending the best/most appropriate way to test a problem? Are you thinking of scenarios or perspectives others arn't? Are you making sure you are seen as a valued asset within the team and not just a rubber stamp? What I must stress though, is that there is no "quick fix". The main thing is to build up trust and respect within the team. ...


7

Apart from obvious activities like test data creation, test case execution, bug reports...what other initiatives can a QA engineer , take which will help raise his value to the project/Client. You can only do what the situation and context permit you to do. In some shops testers get to review the Requirements before they are finalized. If that's ...



Top 50 recent answers are included