Recommendations for QA/Staging testing on GameSparks.....
T
Toby Gladwell
started a topic
over 3 years ago
Hi all,
I'm interested in what other people have done in terms of QA on a GameSparks project before releasing . QA directly on dev? It would seem this would cause a blackout period for people working on backend services and with a full release plan that could be a non trivial amount of time.
Are there any plans to have more environments (QA / staging / test) before releasing a live snapshot? A 'staging' environment provides QA with a build/snapshot that is considered to be stable, but not released to the general public. This is important because dev (as we all know) is constantly in flux, unstable, buggy and not ready for prime time.
Thanks!
- Toby
Best Answer
C
Customer Support
said
over 3 years ago
Hi Toby,
You could use Segments, create or modify a batch of players to be part of the QA segment and do your testing on them, for users without a segment (or who belong to the player segment) you can apply normal rules to them.
Shane
1 Comment
Customer Support
said
over 3 years ago
Answer
Hi Toby,
You could use Segments, create or modify a batch of players to be part of the QA segment and do your testing on them, for users without a segment (or who belong to the player segment) you can apply normal rules to them.
Toby Gladwell
Hi all,
I'm interested in what other people have done in terms of QA on a GameSparks project before releasing . QA directly on dev? It would seem this would cause a blackout period for people working on backend services and with a full release plan that could be a non trivial amount of time.
Are there any plans to have more environments (QA / staging / test) before releasing a live snapshot? A 'staging' environment provides QA with a build/snapshot that is considered to be stable, but not released to the general public. This is important because dev (as we all know) is constantly in flux, unstable, buggy and not ready for prime time.
Thanks!
- Toby
Hi Toby,
You could use Segments, create or modify a batch of players to be part of the QA segment and do your testing on them, for users without a segment (or who belong to the player segment) you can apply normal rules to them.
Shane
Customer Support
Hi Toby,
You could use Segments, create or modify a batch of players to be part of the QA segment and do your testing on them, for users without a segment (or who belong to the player segment) you can apply normal rules to them.
Shane
-
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 2256 topics