To get started, I just needed this app to do the following:
1. Open my web browser.
2. Load the webpage.
3. Enter the username value.
4. Enter the password value.
5. Submit the credentials.
Yet when it gets to step 3, it ignores the Username field and only recognizes the Password field. After several frustrating minutes, I managed to jerryrig editing it to get the username field recognized and data entered, but a simple right-click in error on my part deleted the test I had working and there was no Undo to bring it back.
How can I feel confidence in an app which doesn't recognize a basic two field logging in screen?
Has anyone else had this problem where only the Password field is recognized? I can't blame the page because QTP, Selenium, and TestComplete all recognized both fields.
1. Open my web browser.
2. Load the webpage.
3. Enter the username value.
4. Enter the password value.
5. Submit the credentials.
Yet when it gets to step 3, it ignores the Username field and only recognizes the Password field. After several frustrating minutes, I managed to jerryrig editing it to get the username field recognized and data entered, but a simple right-click in error on my part deleted the test I had working and there was no Undo to bring it back.
How can I feel confidence in an app which doesn't recognize a basic two field logging in screen?
Has anyone else had this problem where only the Password field is recognized? I can't blame the page because QTP, Selenium, and TestComplete all recognized both fields.
5 Answers, 1 is accepted
0
Steven
Top achievements
Rank 1
Rank 1
answered on 19 Nov 2013, 10:10 PM
can let us know a bit more information - what the code you're trying currently looks like for example, and what errors you're getting?
Steven
Steven
0
Mike
Top achievements
Rank 1
Rank 1
answered on 20 Nov 2013, 03:12 PM
There's no error message. There's simply the inability for the app to recognize a Username field exists on the screen, even when I manually enter a username value into it. I wrote no code, just did a simple recording of a standard, basic, simple login and it can't handle it.
Here's my steps:
1. Launched IE10.
2. Launched Test Studio.
3. Clicked Trial.
4. Clicked Create new project.
5. Clicked OK.
6. Bug #1: Attempted to right-click on TestProject1 rename it to a name I'd used before (but forgotten it had been used), but there's no message telling you you're attempting to rename a project to a name which already exists. It simply prevents you from renaming it. The only way out is to remain mystified, give up, and hit Esc. Why is there no "Sorry, there's already a saved project called [Project Name]." when you hit Enter?
7. Right-clicked and picked Add New Test.
8. Keeping Web selected, I clicked Create.
9. After selecting the newly created test, I right-clicked and picked Record.
10. Bug #2: In the newly launched browser I clicked a bookmark to bring up the app. This all-important step was missed by Test Studio.
11. Bug #3: On the new page my cursor was active in the Username field, and I entered a valid username. This was also missed by Test Studio.
12. I hit Tab to advance to the Password field and I entered a valid password. I clicked Pause, because at this point Test Studio had recorded the steps shown in the attached image.
Nowhere is there any recognition of the Username field except for seeing I had entered text...which it attributes to the wrong field. Again, I'm incredibly disappointed at starting Day 2 with this app and I can't get it to recognize a simple log in process which every other automated application has breezed by without any issue whatsoever.
Here's my steps:
1. Launched IE10.
2. Launched Test Studio.
3. Clicked Trial.
4. Clicked Create new project.
5. Clicked OK.
6. Bug #1: Attempted to right-click on TestProject1 rename it to a name I'd used before (but forgotten it had been used), but there's no message telling you you're attempting to rename a project to a name which already exists. It simply prevents you from renaming it. The only way out is to remain mystified, give up, and hit Esc. Why is there no "Sorry, there's already a saved project called [Project Name]." when you hit Enter?
7. Right-clicked and picked Add New Test.
8. Keeping Web selected, I clicked Create.
9. After selecting the newly created test, I right-clicked and picked Record.
10. Bug #2: In the newly launched browser I clicked a bookmark to bring up the app. This all-important step was missed by Test Studio.
11. Bug #3: On the new page my cursor was active in the Username field, and I entered a valid username. This was also missed by Test Studio.
12. I hit Tab to advance to the Password field and I entered a valid password. I clicked Pause, because at this point Test Studio had recorded the steps shown in the attached image.
Nowhere is there any recognition of the Username field except for seeing I had entered text...which it attributes to the wrong field. Again, I'm incredibly disappointed at starting Day 2 with this app and I can't get it to recognize a simple log in process which every other automated application has breezed by without any issue whatsoever.
0
Steven
Top achievements
Rank 1
Rank 1
answered on 20 Nov 2013, 03:32 PM
Mike, thanks for the info.
You are absolutely correct about the lack of feedback when trying to rename a project to a name that already exists - I'll note that to the development team for future work.
As for your test, a couple of things. First, you'll need to enter the URL into the address bar (or Test Studio's command bar if you're using Chrome or FireFox) to go to your site. In general, Test Studio does not automate against the browser menus, including Favorites or Bookmarks. This is an aspect of our testing philosophy: Test Studio is designed to automate functional testing of the business logic of user applications, rather than controls and tools (like IE) that have already been unit tested.
You'll also want to take a look at this blog post, which talks about recording login pages and specifically the need to click in input fields before typing. The addition of a click in each field prior to input will help Test Studio identify the control properly, and I expect that will allow you to record your test successfully; if not please let us know so we can help further.
-Steven
You are absolutely correct about the lack of feedback when trying to rename a project to a name that already exists - I'll note that to the development team for future work.
As for your test, a couple of things. First, you'll need to enter the URL into the address bar (or Test Studio's command bar if you're using Chrome or FireFox) to go to your site. In general, Test Studio does not automate against the browser menus, including Favorites or Bookmarks. This is an aspect of our testing philosophy: Test Studio is designed to automate functional testing of the business logic of user applications, rather than controls and tools (like IE) that have already been unit tested.
You'll also want to take a look at this blog post, which talks about recording login pages and specifically the need to click in input fields before typing. The addition of a click in each field prior to input will help Test Studio identify the control properly, and I expect that will allow you to record your test successfully; if not please let us know so we can help further.
-Steven
0
Mike
Top achievements
Rank 1
Rank 1
answered on 20 Nov 2013, 04:30 PM
Thank you, Steven. That was a big help. The blog post didn't advance me, but your statements about having to use more explicit actions rather than bookmarks and/or other IE functions did the trick.
To get the username field recognized, however, I resorted to doing every different kind of activity I could on the pair of fields and finally when I had gone through clicking in, clicking out, adding a string, clicking out of that, editing the string, tabbing out of it, setting the values to valid credentials and then submitting them, I had one incident where it properly identified the field name. I manually edited the code to direct it to that field, deleted all the garbage statements, and I had my login test done. YAY!
I was then able to do some quick screen loading tests run on two different drop down menus, and that went well...so I'm researching getting the individual tests to run sequentially. Test Lists seems the logical place to go, but so far its executing only the first test in the list (ironically enough, the Log In script) and ending. But now I am hopeful my problems have resolutions I just need to find.
Thanks again,
Mike
To get the username field recognized, however, I resorted to doing every different kind of activity I could on the pair of fields and finally when I had gone through clicking in, clicking out, adding a string, clicking out of that, editing the string, tabbing out of it, setting the values to valid credentials and then submitting them, I had one incident where it properly identified the field name. I manually edited the code to direct it to that field, deleted all the garbage statements, and I had my login test done. YAY!
I was then able to do some quick screen loading tests run on two different drop down menus, and that went well...so I'm researching getting the individual tests to run sequentially. Test Lists seems the logical place to go, but so far its executing only the first test in the list (ironically enough, the Log In script) and ending. But now I am hopeful my problems have resolutions I just need to find.
Thanks again,
Mike
0
Steven
Top achievements
Rank 1
Rank 1
answered on 20 Nov 2013, 04:41 PM
Mike,
In addition to Test Lists, you probably also want to look at test-as-a-step, which would let you have just one login test that's used by your other tests. I have a blog post that shows that (along with data-binding). This lets you write some steps (your login, for example) that's used by multiple tests. Test lists, on the other hand, are for set of discrete tests that you'd want to run without manual intervention, but each test in a list is a standalone task.
-Steven
In addition to Test Lists, you probably also want to look at test-as-a-step, which would let you have just one login test that's used by your other tests. I have a blog post that shows that (along with data-binding). This lets you write some steps (your login, for example) that's used by multiple tests. Test lists, on the other hand, are for set of discrete tests that you'd want to run without manual intervention, but each test in a list is a standalone task.
-Steven