Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Create build-tests.cmd#7237

Merged
maririos merged 1 commit intodotnet:masterfrom
maririos:testOutsideB
Mar 29, 2016
Merged

Create build-tests.cmd#7237
maririos merged 1 commit intodotnet:masterfrom
maririos:testOutsideB

Conversation

@maririos
Copy link
Member

Build tests as a separate task of build.cmd with a build-tests.cmd script.
When we build passing /p:SkipTests=true the tests are built but not executed. With this change, /p:SkipTests=true allows us to not build nor execute the tests.

cc: @weshaggard @naamunds @chcosta

@maririos
Copy link
Member Author

We want to keep divided the idea of building and running the tests so I added a property called BuildTests.
SkipTests will avoid running the tests

build-tests.cmd Outdated
@@ -0,0 +1,24 @@
@echo off
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make this toggleable like we now do in build.cmd

@if "%_echo%" neq "on" echo off

@chcosta
Copy link
Member

chcosta commented Mar 28, 2016

A few minor notes, but nothing blocking. LGTM

build.proj Outdated
<FilterToOSGroup Condition="'$(_OriginalOSGroup)' == ''">$(OSEnvironment)</FilterToOSGroup>
</Project>
<Project Include="src\tests.builds" Condition="$(BuildTests)=='true'">
<FilterToOSGroup Condition="'$(_OriginalOSGroup)' == ''">$(OSEnvironment)</FilterToOSGroup>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems unnecessary with your changes in tests.builds itself.

@weshaggard
Copy link
Member

FYI @sokket

@jonmill
Copy link

jonmill commented Mar 28, 2016

What about a build-tests.sh script?

@maririos
Copy link
Member Author

@sokket I want to address all the feedback here and once approved implement build-tests.sh

@jonmill
Copy link

jonmill commented Mar 28, 2016

@maririos Would that come in tomorrow then? I'm just concerned about having different ways of building and running tests on each platform (locally) when we don't have that today

@maririos
Copy link
Member Author

@sokket There are not going to be differences on how we build/run the tests as the DW scripts are not changing the way we work by default today. Once we have the different steps of the DW implemented then we are going to enable it.
If you want to start using the DW there are some variables that you can pass to build.cmd/sh to disable some of the steps we currently run there.

@maririos maririos merged commit 814247f into dotnet:master Mar 29, 2016
@maririos maririos deleted the testOutsideB branch March 29, 2016 17:32
@maririos
Copy link
Member Author

maririos commented Apr 7, 2016

@weshaggard After some tests and talking to @dsgouda perf testing was not broken by my change, but for consistency I moved PerfTesting.targets to build.proj
See #7565

@karelz karelz modified the milestone: 1.0.0-rtm Dec 3, 2016
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
Build tests as a separate task of build.cmd with a build-tests.cmd script. 
When we run build.cmd passing /p:BuildTests=false the tests are not build.

Note: the property Skiptests=true only disables the execution of the tests.

Commit migrated from dotnet/corefx@814247f
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants