Tag Info

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

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

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

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

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

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

In actuality, the usability issues only come into play in a very specific case. In most cases, providing a default for a radio button list is actually a straightforward logic issue. Here are all of the parameters I can think of (in order of precedence): Is the user required to provide a choice? If no, then a default selection should never be ...

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

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.

There appears to be a VS Powertool TFS Tester Power Tool-Auto Create Test Cases from PBI Acceptance Criteria in beta that will allow for this to be done. http://visualstudiogallery.msdn.microsoft.com/5826c7c8-852e-4239-96bf-e2ba4ab9dab6

I'd suggest using a modelling tool to perform Model-based testing; we use one called Direct-to-test (DTT) at our workplace. Basically, you can set up a path through the application and specify what should vary based on what configuration files, proving therefore that you've covered every configuration file option (usually a cluster of nodes at the beginning ...

For me the CAPTCHA consists of different sub-modules: generation of the CAPTCHA content as text representation plus some random elements like colors/noise that is added to the image. generation of a CAPTCHA image that will be presented to the user CAPTCHA decision logic/controller that decides if CAPTCHA is entered ok/not ok/create a new CAPTCHA If ...

Example for manual testing, if you mean it: TC1: try to enter the captcha right, expected: you are allowed TC2: try to enter the captcha wrong, expected: you are not allowed TC3: try to enter the captcha with Upper/Lower Case Mix, expected (depends on reqs, mostly): you are allowed TC4: try to proceed without entering, expected: you are not allowed.

You can get ideas from Android unified testing initiative It has a comprehensive list of tests for Android applications. And here are some types of Android application tests from the AQuA website: 1.1 OTA Install 1.2 Long launch time 3.1 Send/Receive Data 3.4 Resource downloading 5.2 Message – Receive 5.3 Incoming call 6.1 Memory card operation ...

Rodrigo, I think you may have a bit of confusion about unit tests and functional tests. Here's a short definition to work with: Unit test - exercises a single unit of application code. Does not invoke or use the application interface. functional test - exercises a function such as "Save", usually via the interface. The unit test is there to check that ...