1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.
igeAutoTest
C++ extension Firebase Auto Test Lab for 3D and 2D games.
Before running this tutorial, you have to install igeAutoTest
[pip install igeAutoTest]
Functions - [DEV]
- First, you need to impor the module
import igeAutoTest - Helper function
- Check if the game is running with Auto Test or not
auto_test = igeAutoTest.isLoopTest() - Capture the screenshot, the image will be saved under .jpg format with the name based on the system time
igeAutoTest.screenshots() - Write message information to a results file, in string format
igeAutoTest.writeResultsTest(message) - Finish the auto test loop, all the result information and screenshot will be upload to Test Lab firebase console
igeAutoTest.finishLoopTest() - The default test loop result should be (result.json)
{ "Adjust": { "adid": "4f05a489cecc11a55b9b3a8f4210c1f1", "debug": true, "event": [], "secret": "(1, 1588245832, 1151454453, 1814556983, 1969935874)", "token": "7m5evag9v7k0" }, "Applovin": { "banner": "7f7bd2e768a442b5", "interstitial": "e1eb7ecd4a858332", "rewarded": "042ce899efe8b87e" }, "Facebook": { "id": "321633655547110" }, "GameAnalytics": { "debug": true, "event": { "complete": [ "world01" ], "fail": [], "start": [ "world01", "world02", "world03", "world04" ] }, "game_key": "02e1f6be051f6035a1f2c1479c40a086", "secret_key": "e3dbce0764a99a0ba5de331d1c02b363c938e614" }, "Result": "Success" }
- Check if the game is running with Auto Test or not
The checklist [PLANNER / QA / DEV]
-
Mandatory
- Result = Success
- has the screenshot capturing throughout the auto test run
- the video
-
Adjust
- debug = false
- has the correct token / secret key
-
Applovin
- we should have correct the banner / interstitial / rewarded key
- show ads when the game has them supported
-
Facebook
- has the correct Facebook id
-
GameAnalytics
- debug = false
- has start / complete event before send the build to Ketchapp
-
Depending on the feature supported, we should have some modules disabled
Reference
Metadata
Release files for igeAutoTest 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| igeAutoTest-0.0.4.tar.gz | 6.8 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| igeAutoTest-0.0.4-cp39-cp39-win_amd64.whl | CPython 3.9 | CPython 3.9 | Windows x86-64 | Details |
| igeAutoTest-0.0.4-cp37-cp37m-win32.whl | CPython 3.7 | CPython 3.7 pymalloc | Windows x86-32 | Details |
Total release size: 114.6 kB
Release files / igeAutoTest-0.0.4.tar.gz
| Download URL | igeAutoTest-0.0.4.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c0ac73b1795d369ca26fdf7487b9bd8e39a697a2f9b8c612c538ef5c6c350c1
|
|
BLAKE2b-256 checksum How to use checksums |
e5b2e45ddaae6cbcca93aee62e9889f53b3c9e5e9410acb7b1b625775560d0e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.4
|
Release files / igeAutoTest-0.0.4-cp39-cp39-win_amd64.whl
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | igeAutoTest-0.0.4-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 49.0 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
3cb0b39cbf31bb5e5055fcbd9f46ca2578651c74278c40cd3d9587ca0e0a629c
|
|
BLAKE2b-256 checksum How to use checksums |
5bdc1622c0655833a063c2bafe09bb2fa72f6051b1cde888a21ba512e4222f44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Release files / igeAutoTest-0.0.4-cp37-cp37m-win32.whl
| Download URL | igeAutoTest-0.0.4-cp37-cp37m-win32.whl |
|---|---|
| Size | 58.7 kB |
| Tags | CPython 3.7 CPython 3.7 pymalloc Windows x86-32 |
|
SHA-256 checksum How to use checksums |
db38e8471bec14154d8455dfc59ac6805d09d0a199d2588c7ddba0969e58df30
|
|
BLAKE2b-256 checksum How to use checksums |
a83b4d54eb81eebf0c4b3e23d8dd0e12df9e8c9c3604c41561d1ea452b860e74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.4
|
Security for igeAutoTest 0.0.4
Upload timing
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.