Lets say we have a login page and we have written 5 TC's to validate Login page
and login page have below components/ details
eg: Title, header, image/logo, username field, password field, login button, forgot password link, help, etc..
so now i need to measure whether all above components/details are covered from my 5 TC's or not
and same above i need to perform for all screens in the app and provide the GUI coverage from my functional TC's
please suggest tools or good approach to do this
Related
I use spring-authoriation-server 0.2
I need to implement a login workflow which is based on a user-interaction on his mobile phone.
Which means instead of username/password custom page, I need to generate some information, and show as QR code. Then a user scans it, and can login.
Now, I have some problems to find the right place in the authorization server where I can integrate own workflow into the login page. I need to wait for the user, and then create the authorization code for the client. So any hints?
Scenario: Login - Click on Add Button - Enter Details - Click on Save Button
10k user
Do I really need 10k login credentials to perform this task or a single login credential can also work?
Does this make any difference in performance metrics?
We don't know, ask your application developers.
Personally I would go for 10k logic credentials as I do believe that a well-behaved performance test must represent real life usage of the application with 100% accuracy and each thread (virtual user) must represent a real user with all related stuff like:
its own credentials
browser-specific entities like:
cookies
headers
cache
handling of embedded resources
handling of AJAX calls
etc.
user-specific entities like:
distribution of scenarios and workload
think times
etc.
No you cannot use same credentials to test the multiple user login . However you can check the performance of the app via logging in same user multiple times , but if you need to test for multiple users you need to login with different credentials.
Giving you an example for different users there can be different data for example Facebook , for Facebook user is directed to homescreen where he/she sees different posts , but the feeds screen will not be same for all the user , data will be different.
so to check efficiently you need to login with different credentials to check the multi user functionality.
I am trying to make the Pre-launch report work well to cover more screens (beyond the signin screen) by providing Sign-in credentials, however after providing the testing account the crawl still cannot beyond the Sign-in screen. This is my configuration:
I can confirm the username/password resource name are correct, but in my app, they are in two separated screens.
I.e.: Input username (actually it requires a phone number) first then tap on Next button in this screen to see the screen for typing password (actually it is the 2fc via SMS),
and after typing in 2fc, the app logs the user in automatically, so there is no Sign-in button.
My question is does Google supports my use case stated as above? I.e.: if username and password are not in the same screen, is Google still able to crawl beyond the sign-in screen?
The crawler will use the provided sign-in credentials when it matches the corresponding resource id on a given screen. So, having username and password on two different screens is not a problem. The tricky part is getting from one screen to another (in your case, it is clicking the Next button) such that the crawler has an opportunity to type in the password. If the crawler does not perform this step on its own, you can guide it with a Roboscript - that is, instead of using sing-in credentials, record a Roboscript in which you type in the username, click Next, type in the password (basically, the steps you mentioned above), and then upload this Roboscript for your pre-launch report.
I am making a bookmarklet, which calls a Google App Engine app. The GAE app uses login information, which I want to store in bookmarklet, so when user first clicks bookmarklet,it asks for login info, but from next time onwards it automatically supplies it.
The difficulty of a bookmarklet directly storing data is that it can only store data in cookie or in localStore, both of which "belong" to whatever page it is currently on. That means it won't work again the next time you use it on a different page, and it also means the page you are on can access the data, which is generally very bad for security.
There are two basic ways your situation is generally handled. The two main ways are:
1.) The application used keeps the user logged in with a cookie. The login information is not stored in the cookie; only a session ID is. This is like when you return to many popular websites, you don't have to log in again. Very often these types of bookmarklets open a small popup for the user which contains a page from the app. If the user is not logged in, the app prompts the user to login first. The bookmarklet in fact knows nothing about being signed in or not.
2.) Each bookmarklet is custom created for each person. So my bookmarklet would be different than yours. The difference is simply that mine will contain my login info in the code, and yours will contain your login information in the code. In fact we would each have to login to the app first before we can get our own personalized bookmarklet.
Generally, option 1 is better and easier and more secure.
If I understand it correctly,this Might help you. http://ajaxian.com/archives/whats-in-a-windowname
It allows for storing data in windowname in JS. Allowing for access of up-to 2 MB of data (A lot more than cookies can hold) and I believe can be used across tabs...
I'm working on a site that requires the user have a unique username to use all services on the site. They cannot self-change this username for community fairness.
We would like to allow users the simplicity of registering/logging in using their facebook accounts, but this username requirement is obviously a hurdle.
The only idea I have come up with is after the connect process, send the user to a final step page where they enter a username. The only downside to this is that the user has the ability to navigate away before entering a username, meaning we need to add further layers of checks to several site functions to ensure a user has a username, and prompt for one if not.
Any ideas on how to streamline this during the connect process? Any site examples of similar implementations where auxillary info is required to use some or all site features?
Have you looked at Facebook's registration plugin?
The Registration plugin allows users to easily sign up for your
website with their Facebook account. The plugin is a simple iframe
that you can drop into your page. When logged into Facebook, users see
a form that is pre-filled with their Facebook information where
appropriate.
https://developers.facebook.com/docs/plugins/registration/
The plugin also allows you to add custom fields so you could simply add your username field.
There are a load of advanced features including validation, here's an example in the Facebook documentation that includes the username field and checks to see if it's available
https://developers.facebook.com/docs/plugins/registration/advanced/#async