Unit test report feature does not display classname
Summary
New unit report does not display the class name of failing test. So it's not easy to determine, which test is failing, especially if you have hundreds of tests.
Steps to reproduce
Execute a failing maven surefire test, that is failing
What is the current bug behavior?
The test class is missing. Only the test method is displayed
What is the expected correct behavior?
(What you should see instead)
Relevant logs and/or screenshots
<?xml version="1.0" encoding="UTF-8"?>
<testsuite xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd" name="de.knowis.cp.common.consumer.openwhisk.service.OpenWhiskServiceUpdateActionTest" time="0.094" tests="10" errors="0" skipped="0" failures="1">
<!-- ... -->
<testcase name="testUpdateActionHandlingHttpClientErrorException" classname="de.knowis.cp.common.consumer.openwhisk.service.OpenWhiskServiceUpdateActionTest" time="0.022">
<!-- ... -->
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
~$ sudo gitlab-rake gitlab:env:info
System information System: Ubuntu 16.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.4.4p296 Gem Version: 2.7.6 Bundler Version:1.16.2 Rake Version: 12.3.1 Redis Version: 3.2.11 Git Version: 2.18.0 Sidekiq Version:5.1.3 Go Version: unknown
GitLab information Version: 11.2.3-ee Revision: aadca99 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.8 URL: https://HOSTNAME HTTP Clone URL: https://HOSTNAME/some-group/some-project.git SSH Clone URL: git@HOSTNAME:some-group/some-project.git Elasticsearch: yes Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: XXX
GitLab Shell Version: 8.1.1 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
~$ sudo gitlab-rake gitlab:check SANITIZE=true Checking GitLab Shell ...
GitLab Shell version >= 8.1.1 ? ... OK (8.1.1) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 19/6 ... ok 19/7 ... ok 19/8 ... ok 19/9 ... ok 18/25 ... ok 18/26 ... ok 17/30 ... ok 17/32 ... ok 18/33 ... repository is empty 19/34 ... ok 13/36 ... ok 19/37 ... ok 19/38 ... ok 20/39 ... ok 19/40 ... ok 19/41 ... ok 13/42 ... ok 17/43 ... ok 17/44 ... ok 17/45 ... ok 19/46 ... ok 13/47 ... ok 19/49 ... repository is empty 17/50 ... ok 13/52 ... ok 17/53 ... ok 18/55 ... ok 20/56 ... ok 22/58 ... ok 24/59 ... ok 18/60 ... ok 13/63 ... ok 17/64 ... ok 34/65 ... ok 34/66 ... ok 13/67 ... ok 13/69 ... ok 13/70 ... ok 20/71 ... ok 17/74 ... ok 17/75 ... ok 45/76 ... ok 17/77 ... ok 19/78 ... ok 19/79 ... ok 19/80 ... ok 45/84 ... ok 46/85 ... repository is empty 18/86 ... ok 46/87 ... ok Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 19/6 ... yes 19/7 ... yes 19/8 ... yes 19/9 ... yes 18/25 ... yes 18/26 ... yes 17/30 ... yes 17/32 ... yes 18/33 ... yes 19/34 ... yes 13/36 ... yes 19/37 ... yes 19/38 ... yes 20/39 ... yes 19/40 ... yes 19/41 ... yes 13/42 ... yes 17/43 ... yes 17/44 ... yes 17/45 ... yes 19/46 ... yes 13/47 ... yes 19/49 ... yes 17/50 ... yes 13/52 ... yes 17/53 ... yes 18/55 ... yes 20/56 ... yes 22/58 ... yes 24/59 ... yes 18/60 ... yes 13/63 ... yes 17/64 ... yes 34/65 ... yes 34/66 ... yes 13/67 ... yes 13/69 ... yes 13/70 ... yes 20/71 ... yes 17/74 ... yes 17/75 ... yes 45/76 ... yes 17/77 ... yes 19/78 ... yes 19/79 ... yes 19/80 ... yes 45/84 ... yes 46/85 ... yes 18/86 ... yes 46/87 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.4.4) Git version >= 2.9.5 ? ... yes (2.18.0) Git user has default SSH configuration? ... yes Active users: ... 24 Elasticsearch version 5.1 - 5.5? ... no (5.6.10) For more information see: doc/integration/elasticsearch.md
Checking GitLab ... Finished
Possible fixes
??