GitLab Speed Runs, 5 Feb 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab JUnit Test Reports: Speed Run

Description

In this project I show how to setup a gitlab-ci.yml file to display test results in the test tab of a Pipeline.

The documentation can be found here: https://docs.gitlab.com/ee/ci/junit_test_reports.html#maven

The sample project can be found here: https://gitlab.com/jheimbuck_gl/junit-test-report-demo

A

Hey I'm James I'm, the product manager for the testing group at gate lab today, I'm going to be showing or doing a quick walkthrough of how to set up a gate, lab see, I ya, know to use the names. A unit test reports, feature I'm, just clarify any confusion, and so I'm gonna start with just a really simple project so going from a new project, we're going to create one from template and use the spring template.

A

That's here, I've already actually taken that step, and so we have this initial project here, just based off the template, so you'll notice there's no get lab CI mo file there. But let's take a quick look at the source to confirm that we have some tests. We do. We have a couple of unit tests here, which is exactly what we need. So let's go back in and it will go ahead and create a new gate, lab CI mo file.

A

And so we're gonna do a pretty bare-bones file here.

A

Just with a built stage.

A

If we reference the docs for J unit, well, look here we're using maven and we'll have some surefire test reports. So we'll just copy this artifacts reports, Jane unit and the surefire line, and that's really all we need to get going and be able to utilize that J unit report, so I'll go ahead and just copy that over.

A

Make sure we get everything on the right line, all right great, so go ahead and commit that change and with the new gitlab CI llamo file, it should kick off a build for us.

A

So our pipeline is running great, so I'll go ahead and pause and we'll be back when that is done. Running.

A

Okay, so I plain finished, running or on the pipeline view here and we don't see any tests, but if we refresh the page we'll see our tests show up, and so this is the new view that includes the test. Suites, we see the suite in the main, build everything passed great and if we click into that, we can see individual tests that have run. So that's pretty great.

A

So we look back at the pipeline again now I'm going to show off real quick.

A

That we don't have an artifact here that we can download and view, and so we need to make a quick change in our get lab CI mo to expose that and make that downloadable. Let's actually call that in the Doc's, just not in a great way in the Ruby example, it calls out adding this pads on keyword here and then specifying the XML file again, we'll create that. So let's go ahead and get into our github CI mo and make that change. Real, quick.

A

And so all we need to do is after the artifacts and the pads keyword and the same line here.

A

Go ahead and commit that do it as a merge request.

A

And pause the video again and as soon as that pipelines done running we'll be back.

A

Okay, our pipeline is all finished up. Let's go ahead and take a look.

A

And in our job now we have a job artifact, so we can go ahead and take a look at that.

A

We see we have that file up now.

A

Cool alright, so the next thing I want to show is just modifying one of those tests so that we can see a failure. So let's go ahead and jump in.

A

To the test themselves and we'll just change this assert.

A

Whoops have to get me the web ID. Do that, though, all right, we'll change, this assert real, quick just so that it does fail, commit real, quick.

A

And go ahead and submit that Emma and we'll be back soon, as that pipeline is done to show what what happens.

A

So we have a fill type line after we made our change to our test and we can see in the merge request view here. We now have a test summary, so we have one failed or error test out of the total of two tests we expand on that. We can see within the test suite what happened in maven build. There was one error found clicking down further. We can actually see what the error is spring is there? Is that what is expected?

A

It was looking for spring is here, and this is similar to the view of what we saw in the test reports which we can get at by getting into the pipeline and then clicking over to the test job, and now we see this views a little bit different. We see a 50% success rate.

A

We see this is the suite that failed in there one past one failed for a total of two tests and digging in we can see further that we have a failed status on this one with that trace, and so we can get some more information there.

A

Just about understanding what has failed in the test themselves, so that's just a quick overview of using that new j-unit test report of getting at that information in the pipeline, how to get to it from the merge request, we're looking forward to feedback from the community and users about how we can make this feature even better I'll link to this project in the video notes and leave everything right where it's at so you can go ahead and take a look dig around fork. The project, if you want. Hopefully this has been helpful thanks.