Commits

Matt Oswald committed f50c187 Draft

Edited online

  • Participants
  • Parent commits 24372cd

Comments (0)

Files changed (1)

InstallAndSetup.wiki

 * Clone the project somewhere.
 * Download and unpack the latest official release.
 
-==== Source Install ====
+=== Source Install ===
 
 * When including the full source of xUnit++ within your project, it is recommended that you include it somewhere within your project's tree. This way you can keep your version of xUnit++ synchronized with your project.
 
 * Modify your test project's link settings to include {{{xUnit++/bin/xUnit++/xUnit++[.Debug].lib}}}.
 * Optionally (but recommended), include the xUnit++.console project in your build, and modify your test project's build to include running your tests after every succesful build. xUnit++.console will return the number of failed tests, so you can use that return value to halt your build script.
 
-==== Packaged Release ====
+=== Packaged Release ===
 
 * Download the latest release and unpackage it somewhere within your source tree, for example {{{path_to/project_root/external/xUnit++}}}.
 * Create a shared object library project (.dll or .so) to store your tests. xUnit++ comes with a suite of tests for itself; you can use this as an example.
 ----
 ===== Visual Studio =====
 
-Regardless of the path taken to add xUnit++ to your project, you can install the [[http://visualstudiogallery.msdn.microsoft.com/3503c205-256e-4b22-b99b-13aaf257c67a|xUnit++ Visual Studio Test Adapter]] (coming soon). This will automatically discover and run your tests for you using the built-in Text Execution Window.
+Regardless of the path taken to add xUnit++ to your project, you can install the [[http://visualstudiogallery.msdn.microsoft.com/3503c205-256e-4b22-b99b-13aaf257c67a|xUnit++ Visual Studio Test Adapter]]. This will automatically discover and run your tests for you using the built-in Text Execution Window.