Hot answers tagged

17

It is always a very good practice to start testing as early as possible. By not fully implemented if you mean still under development, then I suppose that is not such a great idea. Yes, you can go for incremental build releases for testing, that might be helpful. When you say that your testers all log the same bugs, well there's your problem! Do you ...


16

I think the problem arrives from how you use your VCS: You want to commit your code because you have finished a sub task and want to have it backed up in case of e.g. a hdd crash on your workstation. Your testers see changes in the repo or get an automated build which they test. One solution could be a separate working branch which is work in progress. No ...


13

To me this is a perfect example of what happens when effectiveness of testers is assessed based on the wrong KPI, in this case, a number of bugs reported. In the end it will harm testers, developers, relationships between tester and developers and as a result product quality. To me this is wrong KPI and there is been at least two discussions here why is so: ...


10

For estimation, the following aspects should be taken into account: Domain knowledge of the team and the requirements. Risks associated with the project. Buffer time. Historical Data. the software life cycle followed by the project. There are a number of techniques which can be used for test estimation, namely: 3-Point Software Testing Estimation ...


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 ...


6

Most of the companies I've worked for over the last 10 years are using an Agile approach. In this approach there are several factors to pay attention to such as: favor direct communication over formal processes encourage a team approach sit together I find that in such environments you want to seek out practices such as: pairing on test plans before ...


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 ...


5

It makes zero sense to waste time on testing a feature (and reporting bugs, and triaging them) if development is not finished yet. All this work will have to be redone again when code is finished. Something is strange in your process, if testers have so much time that they create extra work for themselves like that, which has no benefits to the project. Do ...


4

No, it doesn't make sense to test code that you know is incomplete and not ready for testing. But rather than blaming your QA folks... I suggest that you take a closer look at your software development process. It sounds like there is a failure of communication between developers and QA, and a mismatch of expectations. For instance, it sounds like you are ...


3

This question has been asked many times before on this forum. So you should try to research a bit before adding this question. Take a look at Here where there is a list of good thinking tools and techniques mentioned for improving your practical thinking ability. You can start by reading the number of books mentioned here You can also follow many of the ...


3

The fact that multiple testers test the same thing without even talking to each other shows very clearly that the process is broken. You shouldn't have 2 developers develop the same feature independently and you shouldn't have 2 testers test the same feature independently . It sounds obvious, but if 2 people work on the same thing, they need to know about ...


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 ...


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. ...


2

You wish to check your code in to keep it save. The testers test everything they can see, maybe because it is not clear what is not finished, or maybe just for another reason. There are a few actions you can take to stop this problem. You could use Feature branches You only merge the code into “main” when it is finished Other developers can see what ...


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

Google docs, the problem with excel say you have 1000 tests and person A finished 200 and person B finished 143 test cases, now the poor lead has to merge the report, since multiple people can edit google docs, and it is free that is the way to go, in addition people can see status in real time


1

Try to break every functionality, just think how break every section this point is call test case and defiantly it will help you


1

As a tester, I love exploring partially developed code, and giving early feedback to the developer. The key thing, as others have mentioned, is strong communication between developer and tester. I need to know what areas are likely to still be incomplete, so I don't waste time trying to isolate an issue. The developer needs to be prepared to outline what's ...


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 ...


1

Is it normal? Yes and no. I would say that first and foremost if you are in an AGILE environment, the product owner or someone else should be scrubbing duplicate defect reports before committing them. Also, testing tasks should be presenting to QA once a feature is working, not typically before. That just wastes precious QA time and makes the backlog messy. ...


1

I'd say the issue is in the complete process. In your process, you should have a delivery document which explains the SQA team what have been developed, and what is still in development. Using this document, the SQA won't test anything not developed yet. If they absolutely must (due to management constraints) test in advance, you could cut your ...


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.


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 ...



Only top voted, non community-wiki answers of a minimum length are eligible