Within TestCentre, you will see a collection of unit and property tests. Each type of test uses their own testing library. For unit tests, I have used xUnit and I have used FsCheck for the property tests. If you are unfamiliar with either of these libraries, please use the following links:
It is worth pointing out TestCentre uses xUnit's Test Runner for Visual Studio. This means you can use Visual Studio's Test Explorer -- which shows you the project's (unit and property) tests with a graphical user interface (G.U.I.). If you are unsure what that is, below is a screenshot of what it looks like.
As you can see, it is a good way to determine what tests are passing and failing. On top of that, it highlights how the tests are organised within TestCentre.
For more information about Visual Studio's Test Explorer, use the following link:
Table of Contents
As Source Code
SmoulderingBeachBall
SmoulderingBeachBallCLI
- SmoulderingBeachBallCLI Home
- C.L.I. Project Breakdown
- The C.L.I's Flow
- Creating the Input-loop
- Command-Methods Overview
- C.L.I. Validation Overview
- Changing the C.L.I. Icon
TestCentre
- TestCentre Home
- TestCentre Breakdown
- Unit and Property Tests Overview
- Console and Library Tests Overview
As a Command-Line Interface (C.L.I)
- C.L.I. Home
- Add SmoulderingBeachBallCLI to Your Machine
- Using the Console Program
- Console A.P.I.
- C.L.I. Aliases