Qiskit / qiskit-ibm-runtime / 38220110082
91%
main: 91%

LAST BUILD BRANCH: gh-readonly-queue/main/pr-3518-7607b11521051499e71fed08bcfc3cc3719ac2df
DEFAULT BRANCH: main
Ran
Jobs 11
Files 331
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 91.085%. Remained the same
38220110082

push

github

web-flow 
Move integration TestIBMBackend and TestIBMJobAttributes to pytest-only (#3471)

### Summary

Start moving the `integration` suite to `pytest`, starting with the 2
cases that had specific `setUpClass` methods.

This implies that `unittest` will no longer be able to see these two
cases, which is intended as it the rest of the `integration` suite is
expected to converge in the upcoming days.

As this is the first PR of this kind, comes with a set of conventions,
intending for getting all the suite to `pytest` in a consistent state,
refining the conventions later:
* `conftest.py` is reserved for fixtures that are really meant to be
shared (such as getting the integration test dependencies). Other items
go as fixtures in the files that need them
* keep using classes `TestSomething` as the mechanism for grouping
tests, and use class-level fixtures for the times where we need a costly
initialization / cleanup per class. The main intent is to reduce the
tendency to end up with a large number of tests inside a file with no
organization
* when possible, prefer `markers` instead of decorators, as this allows
for more control. `production_only` is the first one (now the
`production` marker).
* aim for fixtures and custom assertions to be fully typed. In this PR,
I also went with typing the tests themselves: might be too much / too
unreadable, we will standardize later. The main benefits is
autocompletion, typing, and more information available when maintaining
tests.

### Details and comments

There are some questions to solve as we convert more items, in
particular:
* whether the `dependencies` fixture is enough, or if we prefer also
some finer-grained ones, such as `service`
* whether it makes sense to treat `test_` devices separately in the
integration tests. They incur in some machinery, and might not be worth
it (and inconsistent as of now, as they are not available under all
accounts, and the resolution might end up in `None`, causing test
errors)

In gene... (continued)

8644 of 9490 relevant lines covered (91.09%)

9.95 hits per line

Jobs
ID Job ID Ran Files Coverage
1 unit-tests_python3.11-windows-latest - 38220110082.1 331
89.4
GitHub Action Run
2 unit-tests_python3.12-windows-latest - 38220110082.2 331
89.4
GitHub Action Run
3 unit-tests_python3.13-windows-latest - 38220110082.3 331
89.4
GitHub Action Run
4 unit-tests_python3.10-windows-latest - 38220110082.4 331
89.4
GitHub Action Run
5 unit-tests_python3.11-macos-latest - 38220110082.5 331
91.07
GitHub Action Run
6 unit-tests_python3.11-ubuntu-latest - 38220110082.6 331
91.07
GitHub Action Run
7 unit-tests_python3.10-ubuntu-latest - 38220110082.7 331
91.07
GitHub Action Run
8 unit-tests_python3.12-macos-latest - 38220110082.8 331
91.07
GitHub Action Run
9 unit-tests_python3.13-ubuntu-latest - 38220110082.9 331
91.07
GitHub Action Run
10 unit-tests_python3.13-macos-latest - 38220110082.10 331
91.07
GitHub Action Run
11 unit-tests_python3.12-ubuntu-latest - 38220110082.11 331
91.07
GitHub Action Run
Source Files on build 38220110082