Tag Info

Hot answers tagged

9

The traditional definitions would be something like this: A test suite is a collection of test cases related to the same test work. You might have a suite for regression, one for build verification tests, a suite that is specific for a component, and so on. A test plan is generally a document which describes testing approach and methodologies being used for ...


9

This is - sadly - rather more common than anyone here would like. It's where I was when I started at my current position: two major applications, both stable, but the company has never had dedicated test specialists before. The first thing I did was make sure that everyone knew there weren't going to be any quick changes. No matter how skilled a person is, ...


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


5

Webdriver is not only more modern. It is future W3C standard. Being able to click on hidden links seems like a misfeature. I would use old version only if newer version was seriously lacking important features without which I cannot live.


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


4

Since Selenium RC is deprecated and you touch on future-proofing, you should choose WebDriver. WebDriver expertise is more valuable to you because it's more transferrable. Yours is a future worth proofing. Over time, WebDriver expertise will only become more common than RC expertise. Subsequent hiring managers in your organization will appreciate this ...


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

In two words- Risk analysis. In a few more words- risk is usually defined as the probability of something going wrong multiplied by the damage caused by this something actually going wrong. Now you can use this definition to come up with more specific guidelines like- Is this feature stable ? Is this feature dependent on other less-stable features ? ...


3

Anecdote: I worked on one project for a national company. Testing was being done and overseen by one of the Big Name consultancies. Their testers were told to take screenshots for every test step. They abandoned this practice as (1) it was taking too much time and test progress was too slow and (2) I was fnding 90%of the defects on the project by doing ...


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


2

If we refer to ISTQB glossary of terms then test suite: A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one. test plan: A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, ...


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

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

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

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

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

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

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


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

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


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

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

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

Why not Testlink? Pros: Every needed function present Possible to add additional fields Possible to manage test-cases related to different projects, test-plans Possible to manage different versions of test-cases Possible to assign test-cases to tester for execution Possible to connect to bug-tracking tools (e.g. mantis, JIRA) Possible to connect to ...


1

Their is more cloud site present for testing in mobile devices. (https://crossbrowsertesting.com/, https://www.browserstack.com/) N.T-- They are all commercial Enterprise service. You can try a demo for these cloud services in some limited devices or some few minutes.



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