Hot answers tagged

5

The question asks whether other test cases can cite smoke testing as a dependency. The answer depends on the purpose of the dependency. If the purpose is to narrow down what your test cases need to cover, that's fine. If the purpose is to exploit a side-effect of the smoke test, e.g. to take advantage of configuring the software in a certain way, or ...


5

Yes, you can do that. For this you need to save your common/shared test steps in a new test case and then change it to a template using 'Mark as Template Test'. Then where ever you need these shared steps, open that test case and in the test step section of that case select the option 'Call to Test' and then select the shared test case template which you ...


3

This looks fine. BDD feature files is meant to be at a level to give useful information to product folks. In each step you can call lower level steps if you want to give more specific information (or more reusable actions) For this one for example Given I am signed in It might just call within it // enter the username GivenIEnterInTheField(string ...


3

I would recommend doing both approaches, for different purposes. Given / When / Then is good for testing communication. This format brings assurance that what you are testing is what the business owner / requirements writer intended. The bugs mainly caught by these tests, IME, are ones where the business owner intended X and the dev did Y. Often, these ...


3

I'm going to skip answering the parts of the question that do not make sense or are primarily opinion based. So, which plan should actually contain Risk Management, or it should be completely a separate document? Most software organizations don't do this at all or are not formal about it, so you can probably do whatever you want. If you think it ...


2

In addition to the above mentioned headers, a test plan should include following sections too along with their description Entry and Exit criteria: for starting the testing phase and calling it out Suspension and Resumption criteria: during testing there may be several instances when you need to suspend your testing because of single or multiple reasons. ...


2

So is there any perfect test plan template which I can use for one website and I am only tester. No. There is no such thing as a "perfect test plan template". Instead of perfection, strive for "good enough for your needs". Since you are the sole tester, start out with something simple. Note what you are testing, when you are testing, the environment ...


2

Test Plan Test Suite Black-box Testing Test Cases Test Plan: In Test plan you can understand whole application, Flow on your android application and after create test plan & test cases. Black-box testing: Testing without having any knowledge of the interior workings of the application is called black-box testing.Black box testing includes only input ...


2

The more detailed the test case, the more time you will spend on revisions as the software evolves. The less detailed the test case, the more you are leaving it up to your testers to read between the lines. Maybe you should try it both ways and see how it goes.


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

It really depends on how you write your test plans. In that specific case, you can at least do preparatory work, with structure, without details, like "create a customer, enter an invalid age, checke there is an error message, enter a valid age, check the creation works". If you happen to need more detail in your test plan(really depends on the shop), ...


2

I would like to propose that you consider what is needed to support an opinion that the quality of what is being delivered is "Good Enough". In as much as we try to develop systems in general with the end user in mind, asking this question helps you to design the type of data you need to collect. I have found that the generic answers that we would ...


2

It does depend quite a lot on the user story, but there are some general guidelines, with more or less the following order of priority: Essential Tests Acceptance Tests - By definition, the user story can't be accepted if it doesn't pass acceptance testing. The exact form the acceptance tests take will depend on the user story: for back end focused user ...


2

Yes, it is an "opinion" based question but I think that there is not a standard answer because in the Agile world the time is divided into sprints and each sprint contains one or more user stories. The point is that the US of a sprint sometimes are more focused on the back end of the product and sometimes are focused on the front end so the effort of testers ...


1

Acceptance tests and Unit tests are critical to testing on Agile teams, but you can't forget to continue to consistently test non-functional requirements (Usability, Performance, etc.) and whatever additional testing needs to be done to ensure there is enough coverage at all levels (subjective per team) to confidently send the completed code to the business ...


1

I don't think that in an official master test plan a smoke test can be accepted as pre-condition for starting with formal test plans, or at least it would be difficult for me to justify a not formalized condition as trigger for a testing session. Everything changes if your smoke test is composed by a predefined sequence of steps but, in that case, you are ...


1

Given the mandate to use Microsoft Office, I'd look at using spreadsheets to manage the test execution, working something like this: The master list of all test cases for the project is either a Word document or an Excel spreadsheet, linked from the Test Plan. Each test run can be either a separate spreadsheet or a worksheet within a single spreadsheet, ...


1

This is a huge question! I've worked at similar places where they want a QA team to work without the QA tools like bug-tracking software, for example. If you're being forced to use Microsoft Office, then it might be worth splitting up the document, so rather than tracking the defects in one test document per iteration, you could literally have one page per ...


1

honestly today I believe that most businesses don't care for many papers, delivered value, go for it. Forget test cases, test plans. A mind map can help you much more Today most environments are agile, no one has time to look at thousands of papers with a lot of text. Using a mindmap you can "draw" your ideas and be faster and intuitive


1

I have been asked to learn about Test Plan, Test Suite, Black Box Testing, Test Cases I would like you to summon our search god, known to us as Google. One query and there is a bucket full of results returned, which have all the information that you need. I expect, most likely your prayer would be answered. Go by this order : Black Box Testing : A ...


1

Generally when it comes to implementation , correct order is : 1 - Create Test Plan 2 - Create Test Cases 3 - Execute Test Cases [It includes all testing. i.e Blackbox] what are the necessary test cases for application testing? Mostly it is depends on what flow and functionality application includes. You can check common mobile application check ...


1

I would rate each of these improvements on 2 dimensions: - The impact to quality if it was implemented - The ease/quickness/cost that the improvement can be implemented If you have any high impact, easy to do items - those are your first priorities. Otherwise, you might want to take the highest from each category. (one easy, one high impact) You probably ...


1

So is there any perfect test plan template which I can use for one website and I am only tester I don't think you will find this perfect test plan on the web. It is upon you to modify the closest one to suit to your needs. I have found this website to be extremely helpful which searching for artifacts/resources related to SW Testing : Vietnamese Testing ...


1

For Medium size web application,you can write a test plan from the Software testing help , in which all description wise all field name is displayed and also one sample of test plan is also displayed, you can use it, from the below Link: http://www.softwaretestinghelp.com/how-to-write-test-plan-document-software-testing-training-day3/


1

Coming to this from the safety critical side of the industry I would say that your Risk Management Plan should start with a Corporate level Risk Management Policy that states how you are going to manage the risk aspects of all of your work, for example how risks are categorized, what documentation, testing policies, etc., must be in place and what type of ...


1

For the part of your question "Also we have separate sections for Features to be tested and not to be tested. Is this not redundant with features to be tested? Also if we indicate the list of features not to be tested, why we need to indicate the list f features to be tested? When features are listed in requirement document, obviously all of ...


1

Test Items were: • Version of product (what you are testing at each stage) • Design decomposition (relationship of specific modules to test plan, test cases) • Limitations of product under test (restrictions, assumptions, caveats, etc.) • Other product-level restraints on testing


1

@Eduard Florinescu In my view as a Test Engineer - I have to be more detailed oriented with requirements and clear in understanding of product vision, goal & business values. Psychological - Keeping mind fresh is more important task for tester, I suggest you follow these idea. 1) Think a product in 3D view, you view more dimensions.( 3D can be any new ...



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