At some point, tests did not run anymore because they were not identified. The CI job itself passed, but it could have been noticed by a sudden decrease in test coverage of 0%. Issue was fixed in https://github.com/parse-community/Parse-SDK-Android/pull/1216, however this also means the CI is not failing due to 9 failing tests.
Tests fail, apparently due to the way the testing is conducted, not because the SDK code itself is faulty. Hence this issue is only labelled as ci. If it turns out that there are actual issues in SDK code, this will be labelled as bug.
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
New Issue Checklist
Issue Description
At some point, tests did not run anymore because they were not identified. The CI job itself passed, but it could have been noticed by a sudden decrease in test coverage of 0%. Issue was fixed in https://github.com/parse-community/Parse-SDK-Android/pull/1216, however this also means the CI is not failing due to 9 failing tests.
Steps to reproduce
See https://github.com/parse-community/Parse-SDK-Android/actions/runs/10436358169/job/28901326229 for the failing tests, or for better overview https://github.com/parse-community/Parse-SDK-Android/pull/1216/commits/fdd94883ad0057fcd183b89bf7aea69ddb5bdac4 which shows the 9 tests.
Actual Outcome
Tests fail, apparently due to the way the testing is conducted, not because the SDK code itself is faulty. Hence this issue is only labelled as
ci
. If it turns out that there are actual issues in SDK code, this will be labelled asbug
.Expected Outcome
Tests should pass.