| Message ID | 20201009205513.751968-4-crosa@redhat.com |
|---|---|
| State | New |
| Headers | show |
| Series | Acceptance Tests: improve usage on GitLab CI | expand |
On 10/9/20 10:55 PM, Cleber Rosa wrote: > Avocado will, by default, produce JUnit files. Let's ask GitLab > to present those in the web UI. https://gitlab.com/philmd/qemu/-/pipelines/200764992/test_report Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com> > > Signed-off-by: Cleber Rosa <crosa@redhat.com> > --- > .gitlab-ci.yml | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml > index bed5fe6161..7d4b2ced9e 100644 > --- a/.gitlab-ci.yml > +++ b/.gitlab-ci.yml > @@ -53,6 +53,11 @@ include: > paths: > - ${CI_PROJECT_DIR}/avocado-cache > policy: pull-push > + artifacts: > + paths: > + - build/tests/results/latest/results.xml > + reports: > + junit: build/tests/results/latest/results.xml > before_script: > - mkdir -p ~/.config/avocado > - echo "[datadir.paths]" > ~/.config/avocado/avocado.conf >
Philippe Mathieu-Daudé <philmd@redhat.com> writes: > On 10/9/20 10:55 PM, Cleber Rosa wrote: >> Avocado will, by default, produce JUnit files. Let's ask GitLab >> to present those in the web UI. > > https://gitlab.com/philmd/qemu/-/pipelines/200764992/test_report > > Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> > Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com> That's awesome - I wonder if the tap reports can also be read? Reviewed-by: Alex Bennée <alex.bennee@linaro.org> -- Alex Bennée
On Mon, Oct 12, 2020 at 02:09:22PM +0100, Alex Bennée wrote: > > Philippe Mathieu-Daudé <philmd@redhat.com> writes: > > > On 10/9/20 10:55 PM, Cleber Rosa wrote: > >> Avocado will, by default, produce JUnit files. Let's ask GitLab > >> to present those in the web UI. > > > > https://gitlab.com/philmd/qemu/-/pipelines/200764992/test_report > > > > Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> > > Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com> > > That's awesome - I wonder if the tap reports can also be read? > Not according to: https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#artifactsreports But, I'm working on further integrating Avocado to other types of tests in QEMU, so users can choose to run test jobs with any combination of test types. A very rough PoC with some unit tests (that generate TAP) being run by Avocado, and the JUnit report being displayed, can be seen here: https://gitlab.com/cleber.gnu/qemu/-/pipelines/201609047/test_report The grand vision is, among other things, to be able run tests related to a given subsystem or feature, say "migration", no matter what type of tests they are. Cheers, - Cleber. > Reviewed-by: Alex Bennée <alex.bennee@linaro.org> > > -- > Alex Bennée >
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index bed5fe6161..7d4b2ced9e 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -53,6 +53,11 @@ include: paths: - ${CI_PROJECT_DIR}/avocado-cache policy: pull-push + artifacts: + paths: + - build/tests/results/latest/results.xml + reports: + junit: build/tests/results/latest/results.xml before_script: - mkdir -p ~/.config/avocado - echo "[datadir.paths]" > ~/.config/avocado/avocado.conf
Avocado will, by default, produce JUnit files. Let's ask GitLab to present those in the web UI. Signed-off-by: Cleber Rosa <crosa@redhat.com> --- .gitlab-ci.yml | 5 +++++ 1 file changed, 5 insertions(+)