Tag Info

New answers tagged

1

Frankly speaking, too many test plans are a lot of boilerplate without substantive information. Over the years, I've tried to strip out rote process information entirely or place it in a separate process document and focus on these key items in the test plan document. (I'll mention here that documenting a test plan is the final step. Most of test planning ...


0

To answer this you have to ask a lot of questions. I would start with the following questions. What is changing? How significant of a change is it? How large of an impact will the change have? How much risk of a defect is in the change? What is the consequences of a defect in this piece of the code? Will people be fired if you miss something?


0

It is a very broad question. You may use some of these tools: Agile/Scrum project management tool Version One. They have free and paid versions. I find this project management to be very effective and user friendly. When choosing for bug tracking tool, find the best match for your team. Jira is one of the best one out there. Mobile/Device Testing You can ...


1

Those sound like reasonable criteria, but our opinions are not as important as your stakeholders'. You were asked to do this for a reason; perhaps someone in the organization thinks this large company's test process is deficient in some dimension. Why not ask them whether there are any criteria besides the ones you listed that they would like for you to ...


1

The ISO 9126 has some kind of templates for its own implementation: metrics that can be used for each quality characteristics, guidelines for the measurement process and usage of the standard. You will need a full version of the standard to get it, because these are rarely described in the comments on the standard. So buy it, or grab a copy in your company ...


2

As an initial guesstimate I would equal the developers estimation. Obviously you should adjust it to your circumstances, for example do you need to develop automation ? if yes do you have an infrastructure you are familiar with ? is this a new project ? how complex is it compared to previous project you tested ? are there special risk regarding quality like ...


1

This depends on many factors. How accurate and reliable are developer estimates? For throughout the testing needs to be? How efficient you are in testing compared to the developer? How you count time needed for bug fixing and re-testing (and re-fixing and re-re-testing); is it development or testing time? Old rule of thumb is to take original development ...



Top 50 recent answers are included