fsharp/tests/fsharpqa
Phillip Carter 7780047000
Be very literal about the LangVersion string (#7895)
* Be very literal about the LangVersion string

* Skip timing test
2019-11-21 20:59:11 -08:00
..
Source Be very literal about the LangVersion string (#7895) 2019-11-21 20:59:11 -08:00
testenv Reconfigure Legacy MSBuildReferenceResolver to be API-driven (#6898) 2019-06-02 11:28:28 -07:00
comparer.fsx Add --langversion:?|version|latest|preview (#6790) 2019-05-26 21:15:32 -07:00
fsharpqafiles.csproj Add support for --pathmap (#6609) 2019-04-23 17:27:21 -07:00
readme.md update testguide.md relative to fsharpqa tests (#5160) 2018-07-12 22:57:41 -07:00
run.fsharpqa.test.fsx update perl test runner (#7779) 2019-10-30 15:26:33 -07:00

readme.md

F# QA Tests

Layout description

Source/test.lst

This file is the entry point in the test discovery system of F# QA suite.

About the format:

  • lines starting with # are considered as comments,
  • each entry is defined in a single line
  • elements within entry are tab delimited ** first element is a comma separated list of tags classifying the tests of that entry ** last element is the folder containing the tests
  • each of the entries' folder have a env.lst file listing individual tests

env.lst

(TODO, describe the format)

Workflow when adding or fixing tests

You can use run.fsharpqa.test.fsx script, and edit the end of it to specify which classifying tag you are working with. Evaluating the script should run the relevant tests.

A convenience "fsharpqafiles.csproj" project is located in the fsharp.sln solution, the only purpose is to facillitate navigation to test files that frequently need to be edited from within the IDE/text editor environment.

  • edit Source/test.lst, find the entry you like to work with and give it a unique tag (e.g. "RERUN")
  • within the suite, if you are only interested about a specific test, you can comment lines in env.lst files by prepending those with #
  • adjust run.fsharpqa.test.fsx and evaluate it
  • open ../TestResults/runpl.log which should contain failures or be empty (in which cases, your tests are passing).
  • adjust the tests and repeat from step 2

(TODO, provide some guidance about how to define env.lst files)