Hi TestDesking Enthusiasts !
I was wondering on how many different areas does a tester might leverage features of testersdesk.com while testing any typical web application and I started with an email service provider (gmail). (Note: Usage of TestersDesk doesn't confine to just web applications, infact any application with its functionality exposed through screens of fields can benefit from TD).
Coming back to the point. Let us closely examin all features of a typical E-Mail service provider (gmail) right from Registration to requesting for deactivation of our email account and identify...
- All different areas where Test Design and Test Data tools of TestersDesk can be leveraged.
- Areas where TestersDesk can help us prepare better test data which yield better bug removal efficiency.
Scenario: Possible test cases for Registration Screen
Let's examin possible types of test data required to test a registration page for gmail account. If you look at top right corner there is something called 'Change Language' option (list box), and if i am not wrong there are 52 values in that list box. Which means you have to prepare following (i.e we need to generate test data in 52 different languages and test it).
Do you think like "What the heck ! who the hell on earth does all that stuff ! ". Ok ! what do you think google releases without testing them all ? I don't think so ! This implies guys at google must have undergone all the pain or used some or other technique to generate test data for all 52 languages.
Lets examine test data required for one language (English-US), only for registration page.There are 9 text fields in total, out of which one field is 'Terms of service' field. Here is a list of features of TestersDesk which can be used (classified according to Category of Tools).
| Field Name | Category | TD Feature |
|---|---|---|
| First Name | Test Data | Person Name Generator |
| Last Name | Test Data | Person Name Generator |
| Desired Login Name | Test Data | Person Name Generator |
| Desired Login Name | Test Data | Email Address Generator |
| Change Password | Test Data | Password Generator |
| Re enter Password | Test Data | Password Generator |
| Answer | Test Data | Quantified String Generator |
| Secondary E-Mail | Test Data | Email Address Generator |
| Word Verification | Test Data | Quantified String Generator |
| All above fields individually | Test Data | Quantified String Generator |
| All above fields together | Test Design | Pairwise TestCase Generator |
Lets roughly estimate the test data required to be generated for registration page alone.
Test Data = (All types of test input values for each field ) * (8 fields) * (52 Languages)
Lets imagine the time it would have taken for guys at google or where ever to prepare this amount of test data just for one page.
Using TestersDesk any novice could generate this test data on the fly, now do you think we need to discuss more on how much time is saved... stuff like that , that should be quite clear by now, isn't it !
I think we need to discuss more on every area where we can leverage TD.
All that one need is little understanding of areas where tools at Testersdesk can be leveraged.
How about gaining little insight into using TD for Login Screen in next post?
There are lot of other features yet to be explored, keep visiting.
Until then, Happy Testdesking !
Virtualkey
Posts
