Tag Info

Hot answers tagged

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


8

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


8

It depends, and there are no industry standards. Seriously. Any metric can be gamed (and will be, if you use it for assessment). I'm not aware of any standard approaches, not least because the teams are - or should be - evaluating themselves regularly and looking for ways to improve their own processes (if they aren't then they're probably using ...


7

First off, everything I say here should be checked against your job description - that's going to tell you what your employer expects of you. As a lead, you probably don't have hire/fire responsibility (that usually goes with the manager title), so your employer's expectations will probably fall into these areas: resource management - making sure that ...


6

I'd suggest you start with the software quality blogs and forums around the Internet. Some of the online portals I like are: Joe Strazzere's All Things Quality The Software Testing Club portal (they have a pretty good forum, too) The Ministry of Testing portal (their listing of tools is long and could use more detail, but has a lot of information condensed ...


6

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

I'm going to start with my standard response: it depends. I'm assuming you're talking about computer games and not board or other kinds of games, but the computer game industry has something of a reputation for using a lot of unskilled testers. That reputation comes from the fact that the large game development companies can call on gamers who think it ...


5

Instead of an "either/or", it is better to think of test case or scenario testing as a tree structure: Trunk: This is common test set that are always run (e.g. launch the application) Branch: These are major scenarios that have few common tasks (e.g. "admin" vs "user" scenarios) Branch: ... (if needed) Branch: ... (if needed) Twig: Test cases that are ...


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

As you say - 'it depends' but a few comments from my experiences: If you supply exact steps and data then what is the point of UAT? You might as well get your testers to run the scripts. I'd rather give the users some training on the system and give them scenarios to follow - which will have been developed with their input. Should anyone be able to run 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 ...


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

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


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

Here are pros and cons of running tests in a sequence. I understood you ask in a context of automation, not manual execution. Pros: Execution time can take shorter, because previous test sets prerequisites for the next one. Cons: Harder to run in parallel. If you have a sequence of tests that depends on each other, you cannot run them in parallel. You ...


3

This is a pretty common situation - and one I've dealt with myself. Based on your comments and the question itself, I can offer a few suggestions. Document your test dependencies - if you're going to be running tests that depend on the result of other tests, make sure you document them. Build in per-test checks - it's a lot more complex to check the ...


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

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

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

It is probably different for each organization/team/product/process, but here is a typical process I have used (starting from new functionality): Identify the key test parameters such as oracles, surfaces (variables like platform, inputs, outputs, etc), and risk areas. Explore the function under scrutiny at the time using multiple manual test sessions. ...


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

I found fork on github with clear instructions: https://github.com/rodion-goritskov/test-analytics-ng How to build? You need Maven (http://maven.apache.org/) to build the test-analytics-ng project. Clone this repo If you have Maven version 3.0.X change the appengine-maven-plugin version in pom.xml to 1.8.3-maven3.0 Run mvn compile Run mvn package How ...


2

Ok, I edited this answer based on your clarified question. (It makes sense now.) It is important to treat automation as a tool rather than a "tester". A major fallacy in automation is to treat each of the test cases as pass/fail tests. Instead, it is better to treat them as "trip wires" that simply indicate additional attention should be paid to the test ...


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

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



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