Bug 1403867 - Feature: run unit tests as part of build
Summary: Feature: run unit tests as part of build
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: dotNET
Classification: Red Hat
Component: rh-dotnetcore10-container
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 1.0
Assignee: Severin Gehwolf
QA Contact: jiri vanek
Les Williams
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 14:08 UTC by Tom Deseyn
Modified: 2017-03-20 08:25 UTC (History)
7 users (show)

Fixed In Version: rh-dotnetcore10-docker-1.0-13
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-20 08:25:13 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-developer s2i-dotnetcore pull 20 0 None None None 2017-03-13 14:19:30 UTC
Red Hat Product Errata RHBA-2017:0560 0 normal SHIPPED_LIVE updated dotNET container images 2017-03-20 12:34:48 UTC

Description Tom Deseyn 2016-12-12 14:08:48 UTC
Support running unit test projects by specifying DOTNET_TEST_PROJECTS.
These unit tests are started from the assemble script.

The DOTNET_TEST_PROJECTS is set to a list of test project folders.
For each of the folders the assemble script invokes the 'dotnet test' command. The --framework flag is set to match that of the image (cfr build command).

Comment 3 zzambers 2017-03-15 18:33:07 UTC
Testsuite passed for both 1.0.4 and 1.1.1

1.0.4
https://bugzilla.redhat.com/show_bug.cgi?id=1430300#c4

1.1.1
https://bugzilla.redhat.com/show_bug.cgi?id=1430310#c4

Comment 5 errata-xmlrpc 2017-03-20 08:25:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0560


Note You need to log in before you can comment on or make changes to this bug.