Tag Info

New answers tagged

0

I think all solutions depend on the problems. If I were you I would answer in following way. Find out the motivations why formal QA team and process are planned to introduce, what are the quality problems the engineering team management expect to address Based on the problems, layout the long term targets and short term targets If this is not acceptable ...


0

I am working for a top large enterprise software company. I've worked for internet company and consumer product companies. Assume you mean taking screenshot for manual test execution. I never heard that screenshot is taken even no bug is found. If the intention is to simply prove the test is executed, you team got a trust and management issue, address it ...


0

Defect reporting tools are going to vary at each company. For example; some places use HP's QLM, some places use Target Process, some places just use Word/Excel. (I'm not associated with any of these companies but have used them at clients in the past!) As far as the content goes... you've kind of answered your own question. The report needs to be clear, ...


0

The short answer: Imagine you're trying to guide someone that's blindfolded through an obstacle course. They'll need to know where they are, details about how to move, and information about what to expect at each step. Bug reports are similar; you need to use words, pictures, and video to accurately guide them through what you were doing, what you ...


0

Generic guidelines you can find in a similar question Best guidelines for bug reporting?. If you're looking for examples of bug reports, I would browse through bug reports for open sources and publicly available projects. It actually makes no sense to link such places. Rather, you need to find an application or programming library that you use or are ...


1

What you should do is ask your customers what they want. In this case ask your developers what kind of information do they like to receive about any bug and in what format. Usually prepare a proper story of what you did to generate a specific bug and why exactly do you think it is a bug? What will happen if you don't fix this bug? Maybe make a video ...


0

you should have a look @ http://www.softwaretestinghelp.com or specifically http://www.softwaretestinghelp.com/how-to-write-good-bug-report/ this will help you.


0

First of all: Something like one perfect bug report for all projects and types of applications does not exist. But you can talk with the developers and stakeholders of the project and discuss improvements of the bug reports you create. After a while you will have reports who everyone like. Here is an example how I write a bug report: Preconditions: The ...


0

I'll give you advice, not really full blown best practices. Hope this helps. Managing test cases in a project that has regularly changing requirements is a place where test management ( or ALM ) tools can help a lot. I have used HP ALM and Meliora Testlab in this kind of situations, but probably the IBM support similar features. Any tool with good linking ...


3

The short answer (as others have said) is by any method that works for you. The longer answer is that there are no best practices, only practices that are better or worse in any situation. Some things you can consider: Use version control and maintain branches or labels that match the versioning of the code you're testing. One method I've used ...


1

I totally agree with milinpatel17. There is no specific answer for this. It is up to an individual or a team to decide which format will get their job done in better way for them.


1

In testing, there is no such thing as best practice. There is also a good/better/appropriate practice. To manage tests and link them to the requirements, you can do it in several different ways. Mind mapping your test ideas/cases against requirements. Use xmind, freeplane, etc. Make metrics in excel spreadsheets. Use test management tools like TestLink. ...



Top 50 recent answers are included