summaryrefslogtreecommitdiffstats
path: root/LICENSE.MIT
diff options
context:
space:
mode:
authorAlassane Yattara <alassane.yattara@savoirfairelinux.com>2023-11-09 16:55:44 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-11-09 17:01:18 +0000
commit8b957cf1fe1b075adffa5580d3c6ca31efc842e4 (patch)
tree37c36a0168a9cff7f54b96b9fea95b3eb26cbb84 /LICENSE.MIT
parent5e46a34555d9e823168d3f34388f61dd1bdf8b9a (diff)
downloadpoky-8b957cf1fe1b075adffa5580d3c6ca31efc842e4.tar.gz
bitbake: toaster: fixed: Tests fail when executed one after the other out of sequence
As mentionned in earlier commit, pytest-django takes a conservative approach to enabling database access. By default our tests will fail if they try to access the database, Only if we explicitly request database access will this be allowed, using pytest marks to tell pytest-django our test needs database access. A side effect of pytest mark, is test_case method marked is execute out of scope of its module class, which create an inconsistance sequence and make fails followings tests. The scope of the ordering is global per default, e.g. tests with lower ordinal numbers are always executed before tests with higher numbers in the same test session, regardless of the module and class they reside in. This can be changed by using the --order-scope option from module pytest-order. To fix that i added execution order to tests suite using pytest-order. (Bitbake rev: 8bf32459ab6d8ce7632fca0a4ce0f3aecc7495c2) Signed-off-by: Alassane Yattara <alassane.yattara@savoirfairelinux.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'LICENSE.MIT')
0 files changed, 0 insertions, 0 deletions