Hot answers tagged

11

Palindromes testing is very representative in terms of QA way of thinking. Moreover, writing tests dramatically increase the quality of task specification. When a QA engineer writes test cases, it well may happen that certain case is not covered in initial specs. This is a good reason for QA to come up with idea to improve those specs. So, when you are ...


9

There are at least two (conflicting) ways to think about this: Whether you provide a default depends on the context. If you provide a default, you should be prepared for people to select it even when it's the wrong selection. This is particularly true for user interfaces that require lots of inputs. For example, my company's application has an online ...


8

It's really no different than any other test case. Set up conditions: Check actual result against the expected result So you'll need a list of all the error messages in the system and the conditions that make these errors appear If you want to really test them out then use the FAILURE mnemonic as detailed here.


7

Telling the interviewer what is less important than telling them why. They asked for the two best cases - not just a list of cases. This means that you need to explain to them why these cases are "better" than the many other cases you could have offered up. It doesn't matter if you give good answers if you cannot also explain why they are good answers. A ...


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


6

Requirement Traceability matrix maps the user requirements with the test cases. In simple words, the matrix helps in determining if all the requirements have been covered(i.e there are test cases which can be traced back to the requirements). There are 3 types of RTM: 1. Forward:Requirements->Test Cases 2. Backward: Test Cases->Requirements 3. ...


5

It is hard to say what your workflow will be. I've worked a few SDET/QA jobs, and it really seems to vary quite a bit. I'll try to cover some of my experiences, though, and hopefully that will be helpful. Everyday Things I usually like to start my day with a little bit of blackbox, just to get my brain into motion. I'll spend a little while every morning ...


5

Many of the preceding answers are directed at testing the behavior of the captcha from a customers POV (enter valid, invalid, etc.). But, if you are testing an actual captcha generator that your dev's wrote then you should go deeper. Also, there is some important information about the captcha generator you're testing that would be important for functional ...


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

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


4

The following site offers many sample forms and will allow you to practice your test cases easily. http://www.wufoo.com/examples/


4

I'm currently using Quality Center for test case management, and it has a similar structure. I've found that in the expected result section for each step is a good place to write down some items that you would look for outside of the basic 'action completes without error'. You could mention a few points of other questions to ask while the application is ...


4

To answer the main question, your test is a functional test which uses an expected invalid input condition. Some of my classifications of functional test types are: Functional test - any test of the application's functionality. This can include valid input, invalid input, navigation through the application, and pretty much anything else that involves the ...


4

When possible it is generally a good idea to break out the different assertions into separate cases even though they will repeat the same setup/teardown. The reason is that when one of the assertions fail you want to know that specifically, with text that describes the test and the specific assertion and if bundled together with other assertions, that may ...


3

The purpose of a CAPTCHA is to verify a human is submitting the form. By definition, if you could automate this interaction, the functionality would fail. But you didn't ask about automation, so that's just an aside. Think about it from a functional perspective - does it let you submit when you enter the right input? Does it keep you out if you don't enter ...


3

There are two questions here: (1) test case itself; (2) ability to automate testing. As per the first topic, you just describe it in a form of Actor - Action - Result, e.g.: System redirects to a page XX User types CAPTCHA code into a field [...] System checks answer validity If the key is not valid, System redirects to Step N System redirects to ...


3

See definition of palindrom and think about boundary cases. For instance: What happens to white spaces, and punctuation marks when comparing input with its reversed form? Are they ignored or maybe even not acceptable? Is implementation case insensitive? Usually, both Anna and anna are considered palindroms. This is the task of a tester to explore ...


3

ved, welcome to SQA. You should distinguish between testing the login functionality and merely using the login functionality. End-to-end tests are about ensuring that all the pieces fit together when someone uses the software for a specific task/workflow. If an end-to-end test requires logging in, by all means use the login functionality. However, if you ...


3

This link should be a good start: http://www.softwaretestinghelp.com/test-case-template-examples/


3

Depends on the quality requirements of the project and the maturity of its user stories. If the test has to be done once by the same person who has written the test cases, then documenting the test case steps would not be essential or indespensable. On the other hand, a project requiring different phases of regression testing over a long period of time with ...


3

I think Agile testers should assist their Product Owner with writing Acceptance Criteria in the user stories. If you write scenario's in Gherkin you can create manual test cases that match your four criteria of a test. Scenario: Some action (1. Name) Give I am logged in (2. Pre-condition) And I setup something else When I do some action (3. ...


3

It depends on what the text field is supposed to accept and what it's for. If it's meant to accept specific formats of data, your tests will be different than if it's meant to accept free-form data. For example, text fields are often used for postal code entry. For that, there's likely to be validation that the postal code format matches the official ...


3

A functionality requires validation of system behavior in two (or more) different states. For instance. Let's say in your SUT a user is authorized to use a certain feature only if the user has permission X. To make sure this really depends only on having this permission, you should verify at least two cases, that is your test case have have multiple steps ...


3

To add a dissenting voice - they are there for historical reasons as that's how people thought tests should be written and it also provided a way for tests to be 'measured'. I view such detailed test cases as a waste of time and effort ( the answer from Paul that it's a great practice can be argued against) so I don't see what value you can 'leverage' from ...


3

There are many answers for this question, but first what come's in mind, are: Positive: Data: login: X password: Y User Log in correctly using proprietary data Negative: Data: login: [not registered login] V password: Y User can't log in with unregistered login Data: login: X password: [Bad password] B ...


3

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


3

I would say no. Your tests Should be written with an expected true/false criteria. As such a pass says all it needs to say. If there is a "but" or a "only when" then i would suggest you add new tests to cover those scenarios and improve your coverage. One caveat to this is if you need to add the screenshot to Prove you carried out the test, but that ...


2

Usually social networks / web mail services have a nice many-different-fields reg forms, e.g.: http://mail.yandex.ru/ http://e.mail.ru/cgi-bin/signup?from=main BTW, SO profile page: http://stackoverflow.com/users/1953175/peter-l is a nicest thing to train your cases creation skills, since there are many "hidden" parts, tabs and features which may be quite ...


2

Svetlana, since most publicly-available registration forms for large websites fit your criteria, I'd imagine you could use any of them. You might also consider some Shopping-Carts. Many file upload/download forms (such as those for photos, etc) meet your criteria. Good luck.


2

For this sort of thing you want the ability to enter a set of known data and compare the results against what you would expect the application to output, either at the database or at the GUI. With your example, you'd want to first enter the times into the system by simulating the usual method, and check that the database records match what you'd expect to ...



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