Commit graph

12 commits

Author SHA1 Message Date
Andrew Schwartzmeyer
447b3ef729 Update xUnit runner to netstandardapp1.5
This was enabled in dotnet/coreclr.xunit#12
2016-03-14 16:51:49 -07:00
Andrew Schwartzmeyer
da9c58828e Workaround dotnet/corefx#6603 2016-03-03 17:02:07 -08:00
Andrew Schwartzmeyer
9f2ce63267 Fix xUnit tests for netstandardapp1.5
With the switch to `netstandardapp1.5` framework for the host, the xUnit
test runner broke. For `dotnet test` to work with the .NET Core xUnit
runner, it must continue to target `dnxcore50`. Fortunately, we can
import our project's framework, and make everything work again.

Also improved the `xunit.sh` script to check for dependencies.
2016-02-19 14:40:17 -08:00
Andrew Schwartzmeyer
e6e4dcafbe Build with new framework and new CLI
All libraries now use the framework `netstandard1.5`, and import the
`dnxcore50` and `portable` frameworks. The app that is published,
Microsoft.PowerShell.Linux.Host, that is, the top-level dependency that
emits an executable, instead targets `netstandardapp1.5` and has a new
`runtimes` key so that .NET CLI's `restore` and `publish` commands know
which runtime implementations to resolve.

When switching to the new CLI, we needed to fix how we specified our
dependencies. In particular, the .NET CLI team helped me figure out how
to download packages that are reference assembly only on Linux, with
implementations on Windows. The result of this is the new `frameworks`
setup.

Additionally, we were incorrectly specifying our build dependencies;
that is, projects we also build (not packages). The solution was much
cleaner. We removed the `type: build` section and replaced it with the
version `1.0.0-*` that all our projects currently use.

The `project.json` files also had their names, descriptions,
indentation, and versions fixed.

The build scripts were simplified.
2016-02-18 10:06:56 -08:00
Andrew Schwartzmeyer
dae6e0ebd5 Use Linux.Host in xUnit tests
Make its internals visible to the `powershell-tests` assembly, and use its
`MyHost` and `Listener` classes instead of facades.
2016-02-17 17:03:59 -08:00
Andrew Schwartzmeyer
473ac41630 Initialize the ALC for the runspace tests
This initialization was moved out of the native host and into the
managed host, so the same setup must now be done before tests.
2016-02-17 17:03:59 -08:00
Andrew Schwartzmeyer
c68164f280 Remove Commands.Omi module
This was a temporary work-around that now needs to be removed (mostly
because the xUnit tests are out-of-date because we didn't have a runner,
and it's not worth it to fix them). Rather than let more cruft
accumulate, we need to remove it.

Resolves #551
2016-02-17 17:03:59 -08:00
Andrew Schwartzmeyer
9b9493241d Update xUnit dependencies for dotnet-test-xunit
Add `xunit` and `dotnet-test-xunit` packages. Import `portable-net45`
for `xunit`. Add `xunit` as `testRunner`.
2016-02-17 17:03:03 -08:00
Andrew Schwartzmeyer
a8be633089 Bump packages to rc3-23729 2016-02-02 15:43:54 -08:00
Andrew Schwartzmeyer
71f670f86c Add packages required for updated sources
Commands.Utility now needs Microsoft.CodeAnalysis.CSharp, which doesn't
explicitly target `dnxcore50`, so now Commands.Utility and the packages
which depend on it now much `import` the Portable Windows framework.
This also required adding the aspnetvnext feed.

System.Management.Automation now requires System.Diagnostics.StackTrace.
2016-01-26 16:49:28 -08:00
Andrew Schwartzmeyer
ae9c58e3e3 Remove xUnit reference from csharp/project.json
Currently fails to restore, working on prototype.
2016-01-20 10:14:44 -08:00
Andrew Schwartzmeyer
bbebf2f76a Reorganize tests
- Pester source code moved to `test/Pester`, deleted `ext-src`.
- Pester tests (.ps1 files) moved to `test/powershell`
- xUnit tests (.cs files) moved to `test/csharp`
- Third-party script test moved to `test/shebang`
2016-01-14 17:00:06 -08:00