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


0

Each and every testing timeline is based on requirements , design and development size.It depends on project size, complexity etc. Also remember that not every project require all type of testing. So as a tester first of all it should be clear that which type of testing we will do for this particular project. Test plan is always first step , So once ...


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


1

You can design your test in a spreadsheet and fill out all the combinations. Look for and remove redundant cases. You can incorperate this matrix into your automation by using columns for User/pass to login then try to acess certain pages and use the matrix to assert acess is granted or not. Your automation will be lightweight and rely on the spreadsheet for ...


0

if you (i.e. management) are willing to take some risk you can use N wise testing. But anyway, everything should begin with you having clear understanding of what is being tested. For that you should be organized and be able to track everything, a simple example would be using tables to cross features and test cases (Excel is really good at this)


1

I do not have idea that if you are expert in automation testing or not. If you are then you can create automation script for each role and you can specify diff. logic that if role is call center executive then specified things should be accessible. So you can do that for each and every role. Why I am telling you to use automation because suppose in future ...


1

Your requirements seems to describe document-heavy proprietary process. Unlikely examples of such process would be posted in the open: usually you pay consultants nice hourly rate to teach you/explain you how their process works. Only salesmen (before you fork the money) are free. Call me a pessimist but I know that snake oil is much easier to sell if ...



Top 50 recent answers are included