Tag Info

New answers tagged

0

Test at least one object everyday(maybe a spoon/pen/table or anything for that matter). Generate teat ideas for it and get it reviewed from others. Read about testing - blogs, articles and books. Participate in online discussions, forums and communities about testing. Write about what you learn. Share it with the world. Ask as many questions as you can ...


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


1

One suggestion can be Test Link, its freeware. You can easily install and configure at your end. This tool will help you to maintain a regression repository consisting of Test Case, Test Scripts, Test Run, Bugs etc..


1

I am unaware of any standard definition for "Software Reliability Report". And an internet search doesn't show anything either. So you have 2 options: Ask management what they want in the report, or if they don't know, ask them what the report is for and use your best judgement. Make something up. List of known defects, supported usage scenarios, ...


1

It's possible you're tackling a symptom and not the root cause? Do you have User Stories* and are they managed in some tool? Do you have acceptance criteria for each User Story? Do you formalize the acceptance criteria as Test Cases? Do you "link" each automated test to its corresponding Test Case? If you can answer Yes to all questions then all you need ...


1

The question is a bit theoretical, so I'll start my answer the same way: In theory, or in some projects, testing can be all about generating the great test ideas that will find the most relevant issues. A bit samy way that in theory, or in some projects systematic way of working with requirements will find all the relevant issues and prove that system works ...


0

Others have had had very good points, but I have one more thing to add to managing a huge amount of tests. Make sure you have a way to take one step ( ore few steps) backwards from the test results to form groups. Generally forming groups by functionality of the software works, and you might need to add groups for end-to-end tests etc. that do not fit ti ...


0

One way you can force things is to use mental frameworks, such as ACC or Nouns & Verbs where you come up with two lists and combine the two. Examples are on this cheat sheet. Note the Heuristics section of that cheat sheet also has lots of other ways to approach coming up with tests. These types of models and frameworks help you increase the number of ...


1

You could try reading 6 hats by De Bono - 6 thinking hats or watch this video based on it and adapted to testing by Julian Harty - 6 hats video


1

I'd suggest taking a look at the answer to this question: How can a Software Tester use "Out of the Box" thinking approach to find more bugs? They include general strategies and some specific suggestions. Personally, I find the best way to be a creative tester is to be creative, period - having creative hobbies helps, as does practicing looking ...


0

I really like the videos of James Bach. He has a very unique perspective on the world of software testing. He will challenge your thinking and a lot of the "best" practises in the testing world. Be sure to watch his Open Lecture on Software Testing: https://www.youtube.com/watch?v=ILkT_HV9DVU


0

I dont think so a material would teach/tune your creativity. Try to understand the Business uses of the AUT. Think about possible ways to exploit the App if you were the Real User of that Application. If it is a Banking related application, try to understand the domain knowledge. That will give you more ideas. Try to participate in Bug contests or Sign up as ...


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


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


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


1

Since internally test steps are represented as XML containing HTML, you'd need something capable of parsing this kind of thing (line breaks mine for readability): <DIV> <P>Click edit icon</P> </DIV> <DIV> <P>User is directed to announcement edit page</P> </DIV> <DIV> <P>Click anywhere else on ...



Top 50 recent answers are included