Tag Info

Hot answers tagged

7

To know how to write a test plan one must first learn to plan a test. Planning test is a real thinker task. You should be asking a hell lot of question to learn about the domain of the project. You should learn about the stakeholders of the project. One part of planning consists of test estimation. Here is something that might get you started with it - ...


6

A few thoughts based on my not-quite-ten years experience as a tester and automator: Learn the principles, not a tool - If you understand the principles of automation and how it works, you're going to be in a much better strategic position than if you simply learn an automation tool. You could do worse than to dig through Joe Strazzere's blog and Alan ...


5

If you have specifications that say a confirmation must be displayed, the test fails. If you have user requirements or user expectations that there will be a confirmation dialog, the test fails. In the situation you describe, I would create a bug from the test, but it would have a lower severity rating because it doesn't interfere with functionality. The ...


4

This problem hits everyone with a decent-sized application sooner or later. Some of the things you can do to help manage your test cases more cleanly: Use a self-documenting system - if you're coding Selenium with C#, use the MS XML commenting and something like Sandcastle to publish the documentation that's generated on build to a common site. That way ...


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


3

Naming and separating out your reused parts (tests, keywords for maps). I call this "common" tests/maps. If you already have alot of tests automated then this will be more tedious, but pulling out your unique maps and naming them appropriately will identify the actual controls that are being duplicate tested. Test Naming conventions that follow the ...


3

I agree with milinpatel17' above answer about Test Plan. Test Plan is a detailed layout and strategy to test a product or application. Before you start writing a test plan, consider these points first: Why to test -- objective What to test -- scope How to achieve objective -- required time and money (with number of resources) What approach -- Automation, ...


3

Answer is "when its not feasible/possible to perm a test" It is used for "multi-environment" test-cases and/or if it is some type of generic test-cases script My real example, it would been need to test feature of upload several files same time. But old versions of IE doesn't support possibility to select several files in dialog - so it is "No apply" here, ...


3

As far as I know, there is no such thing as "waterfall testing". The term "waterfall" is used for one approach to the entire software development lifecycle. See the generic Wiki article here. That being said, test design techniques (and most test-related topics) will remain relevant, regardless of the specific process in your company. I would recommend ...


3

Let me give some advice I got from James Bach. He likes to make the distinction between a test plan and the test plan document. A test plan document is the written form of the test plan. This can vary quite a bit depending on the company you work for and in my experience can range from lean or minimal to bloated (I’ve seen so many bloated test plan ...


2

1.In eclipse i have executed the tests they are working fine, how i have to execute them in production server? Your tests can run in every environment. You can have a Selenium Hub and many VMs with different operating systems and browsers. But for the beginning the tests can also run from your local computer. You can choose against what environment ...


2

It may depend on the strategy of your project, but i'd say this test is failed. If the confirmation is part of your specifications/functional need, you can't make this test pass. Imagine this is the only issue in your whole test plan, if you pass the test, then your indicators will be all green for this functionality. Thus, there is no reason to do rework, ...


2

Scrum does not define any processes for testing, its more about a general iterative software development workflow and describes communication points and artefacts. The cycle of a Scrum sprint is that the team commits to a certain number of stories and at the end of their sprint. Those stories should meet the teams definition of done. Which should including ...


2

One thing that is often overlooked is to make use of your coverage tool(s) for more than ensuring that every line of code gets tested - if you configure your tool to produce a separate named output file for each test/test sequence then you can quite easily scan these for lines/blocks that are being tested in more than one test. The other key point is - as ...


2

Some good practice paper you will find at : http://istqbexamcertification.com/ Main thing is concentrate on syllabus given by ISTQB : http://www.istqb.org/downloads/finish/16/15.html As per my experience only some time questions come from practice paper in real exam. Paper is always based in ISTQB syllabus. So read , understand and remember each and every ...


2

You know that (a) is wrong, which eliminates A and D. Not sure why you thought it might be D: it shares wrong (a). So you need to decide between B and C answers. Both suggest (b) and (d). Difference is: Which one to add along (b) and (d)? (e) or (f)? So question is: why (e) and not (f): e. System testing environment has been tested and passed f. Static ...


2

There are many such tools. Basically if you do a search with term "test management tool" you will find a lot of alternatives. There are also many sites listing the tools, but they seem to be biased towards some commercial alternatives. One site with a quite exhaustive listing for Test tools is https://www.testtoolreview.de/en/ The company I'm working in ...


2

No one here can definitively answer an ambiguous question like this. Go ask the person who wrote the test cases, or the test manager, or someone else on the team who has already figured out the answer.


2

I've never heard of "reactive testing" so I'm not sure what exactly that means. Any idea? A blended strategy in the sense of using different test techniques and approaches can be a powerful idea but you (and your fellow testers) need to understand when to use them and when not to. Always make the strategic decision based on the context of your test project ...


2

You already have a very solid foundation to build on, with your impressive knowledge about QA and your professional skills. If you can supplement that with more technical skills and expertise in test automation, you will have a very valuable (and rare) profile on the job market. From my experience with the many excellent people I have had a chance to work ...


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

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


1

It is not "Waterfall testing" , The term "waterfall" is used for one approach to the entire software development lifecycle. The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must be completed fully before ...


1

There is a tool that was just launched by a company called XebiaLabs... I believe the tool is called TestView and does exactly what you are looking for. XL TestView is the first test results management and analysis tool that allows you to define and execute tests across your full spectrum of test tools, then aggregate and visualize the results to ...


1

It grow too long for a comment, so here it goes: Class is like a recipe, objects is like food prepared according to it (instance of a class). You cannot test class, like you cannot taste recipe: only instance of that class is something you can interact with. Of course all instances of a class should behave the same, so you can think about "testing a ...


1

Please note that this is a generic answer; your environment may have its own interpretation that differs. In short a class is the code that describes what the object does. The object comes into existence when the class code is called and one particular object is instantiated. When it is instantiated the object sits in your computer memory ready to do its ...


1

Instead of answering to your individual questions, I will just answer the last sentence: Help you finding the solution. For many Test management tools that integrate with Jira, the way of working will support you well ( you are satisfied with questions 3 to 14 ) What will be ( a bit ) different, is their approach to test management. ( Questions 1 and 2 ) ...


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


1

I would separate the test case into 2: The first one ends with the confirmation message and the second one continues from there on. I would create a bug, link it to the first test case and keep the test case in 'ready', while I would close the second test case. If this is not a major requirement for you, then the test cases can be prioritized, so that ones ...



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