PowerShell/test
Ilya a16fead0a5 Fix error position reporting on classes (#3103)
Interactive hosts expect an `IncompleteParseException` to signal that more input is expected.

When detecting errors, the parser can report 2 positions:
* where the error should be reported
* where the error was detected

Typically these are the same, so most error reporting methods have a single parameter.
For missing braces, the pattern is supposed to be to report the error after the opening brace, but the error is typically detected at the end of the file.

There were a few places where we were not consistent in reporting such errors, this PR corrects those places.
2017-02-13 16:45:00 -08:00
..
csharp Add 'osx.10.12-x64' runtime to project.json files 2017-02-01 17:52:35 -08:00
fullclr Remove trailing whitespace (#3001) 2017-01-16 13:31:14 -08:00
powershell Fix error position reporting on classes (#3103) 2017-02-13 16:45:00 -08:00
PSReadLine Add 'osx.10.12-x64' runtime to project.json files 2017-02-01 17:52:35 -08:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Provide class level coverage data via OpenCover module (#3088) 2017-02-06 23:04:45 -08:00
vs-csproj Add '<Link>' tag to '<Compile>', '<None>' and '<EmbeddedResource>' tags to make those items look similar as when the *.csproj files were in the original project folders. (#2519) 2016-10-21 17:04:05 -07:00
map.json Edit map.json to add in PackageManagement tests 2016-07-12 21:17:11 -07:00
README.md Add test/README.md 2016-03-30 23:30:26 -07:00

Testing

The tests are organized by testing language. Thus Pester tests, which are written in the PowerShell language, are in ./powershell and xUnit tests, written in C#, are in ./csharp. The sanity tests for the Full .NET build of PowerShell are in ./fullclr, and the third-party shebang test is in ./shebang.