The test harness is a great idea, and seems like a powerful tool. But how do I authenticate so I can actually use it? Does everyone really manually "login" every time?
Why isn't there a shortcut using my GameSparks account since I'm already the admin of my project and using a tool authenticated on the GameSparks web site? It seems ridiculous to not have such a convenience for a tool that would otherwise be used a lot.
I already saw the documentation about it, but it doesn't mention where to get any of the required information. How am I supposed to know valid deviceId, deviceModel, deviceName, etc? If I wanted to use something simpler for a human to enter repetitively, like user/pass authentication, how and where do I add a test user so I can login that way?
Hopefully I missed something obvious.
Best Answer
D
Dave Reed
said
almost 5 years ago
In the past I've created a test user with an empty username+password (by sending a RegistrationRequest with its default parameters). You can then log into this user by just sending an AuthenticationRequest with default (blank) parameters). This can be quite useful if you don't need to test something on a specific player.
(Yes, it would be nicer if we could select an existing playerId and have it auto-log-in as that that player, though. Or if we could create a list of players and be able to select one from a drop-down to login)
In the past I've created a test user with an empty username+password (by sending a RegistrationRequest with its default parameters). You can then log into this user by just sending an AuthenticationRequest with default (blank) parameters). This can be quite useful if you don't need to test something on a specific player.
(Yes, it would be nicer if we could select an existing playerId and have it auto-log-in as that that player, though. Or if we could create a list of players and be able to select one from a drop-down to login)
1 person likes this
J
Jason McIntosh
said
almost 5 years ago
Thanks, Dave. Using RegistrationRequest to "create" a test user worked. :) Clunky, but I can live with it.
Jason McIntosh
The test harness is a great idea, and seems like a powerful tool. But how do I authenticate so I can actually use it? Does everyone really manually "login" every time?
Why isn't there a shortcut using my GameSparks account since I'm already the admin of my project and using a tool authenticated on the GameSparks web site? It seems ridiculous to not have such a convenience for a tool that would otherwise be used a lot.
I already saw the documentation about it, but it doesn't mention where to get any of the required information. How am I supposed to know valid deviceId, deviceModel, deviceName, etc? If I wanted to use something simpler for a human to enter repetitively, like user/pass authentication, how and where do I add a test user so I can login that way?
Hopefully I missed something obvious.
In the past I've created a test user with an empty username+password (by sending a RegistrationRequest with its default parameters). You can then log into this user by just sending an AuthenticationRequest with default (blank) parameters). This can be quite useful if you don't need to test something on a specific player.
(Yes, it would be nicer if we could select an existing playerId and have it auto-log-in as that that player, though. Or if we could create a list of players and be able to select one from a drop-down to login)
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstDave Reed
In the past I've created a test user with an empty username+password (by sending a RegistrationRequest with its default parameters). You can then log into this user by just sending an AuthenticationRequest with default (blank) parameters). This can be quite useful if you don't need to test something on a specific player.
(Yes, it would be nicer if we could select an existing playerId and have it auto-log-in as that that player, though. Or if we could create a list of players and be able to select one from a drop-down to login)
1 person likes this
Jason McIntosh
Thanks, Dave. Using RegistrationRequest to "create" a test user worked. :) Clunky, but I can live with it.
1 person likes this
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2486 topics