Tag Info

Hot answers tagged

8

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


6

I do not know what features QC delivers for running automated tests, but this is what I would do to maintain a Selenium test-suite: As a test runner for Selenium just use a unit-test runner in the language you are developing your tests in. Most xUnit-tests runners generate the same result files, which can be parsed by report generators for reporting. To ...


6

For the REST service testing Postman and HttpMaster are good tools. It supports dynamic parameters, validation of response data, various data viewers, etc. If you are looking for performing load testing of the REST services than Grinder and JMeter open source tools can be considered. This data is taken from the post Tools for REST webservice testing


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

As Bookeater says, you absolutely want to unify tools and processes between the teams. That said, I'm going to offer some extra advice because I've been in this situation (and to some extent I am still in this situation). Hasten slowly - Each team has built up a process and toolset that works for them. A newcomer telling them they have to change everything ...


4

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


4

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


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

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

Timebox it and afterwards evaluate. I would say time-box one hour and then see how probable it is the tester will find the steps to reproduce the issue. Often its easier for developers to reproduce the issue, since they understand the code for that part. And they are more proficient in code-debuging.


3

I once tested a Windows client UI by randomly banging on the keyboard while my coworker randomly moved and clicked the mouse. I found bugs that way, and I could reproduce them, but (at least initially) I couldn't tell you the exact set of keystrokes and mouse clicks that triggered the problem. That is monkey testing. Exploratory testing is testing ...


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

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

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


2

It depends. I saw acceptable time/effort ranging from 0 (outsourced testing to almost un trained testers) to infinity and beyond (combined engineering team with engineers that know their way through the code and product). YOUR answer will vary according to (just throwing some ideas): Your skills and knowledge e.g. how familiar are you with the product, ...


2

You are SO going to hate this answer. It is Yes and Yes. There is some possibility to integrate between TFS and fogbugz. http://www.fogcreek.com/fogbugz/docs/70/topics/sourcecontrol/setup/TeamFoundation.html Your goals should be: Maximum tool level integration (to input info only once). Define overlap between procedures and utilize this Minimize ...


2

What are the most important components/parts of a well-written test plan document for a testing project. Consider you are testing a Financial web app. As per IEEE 829 standards, the components of a Test Plan document should be : Test Plan identifier References Introduction Test Items Risks Items to be tested Features excluded for testing Testing ...


2

Testcase format I like one of the following formats: Arrange Act Assert Given When Then These give a clear separation between test phases and steps. How is the test situation setup What is the action under test (try to keep action steps under 10, preferable less) What is verified Details How to write the step details of test-cases greatly depends ...


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

As is often the case, there are competing definitions as to what constitutes each level. If there is a particular model you are attempting to follow you will find the definition(s) vary slightly but follow a general theme. I have tried to outline below: Level One: Initial - Testing is Ad-Hoc. In particular during a crisis, procedures are ignored or not ...



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