From 8d72b14024e8d531b08e4387f89a1167263c2088 Mon Sep 17 00:00:00 2001 From: Franklin Mathieu Date: Mon, 30 Mar 2015 21:13:10 +0200 Subject: [PATCH] Create gh-pages branch via GitHub --- index.html | 61 ++++++++++++++++++++++++++++++++--------------------- params.json | 2 +- 2 files changed, 38 insertions(+), 25 deletions(-) diff --git a/index.html b/index.html index 5f7a573..bcd76bf 100644 --- a/index.html +++ b/index.html @@ -1,6 +1,6 @@ - + @@ -39,12 +39,12 @@

Criterion

-

Build Status -Coverage Status -License -Version

+

Build Status +Coverage Status +License +Version

-

A dead-simple, yet extensible, C test framework.

+

A dead-simple, yet extensible, C unit testing framework.

Screencast

@@ -62,14 +62,29 @@ these suits, and finally call the right functions.

the user would have with other frameworks:

+

+Downloads

+ + + +

If you have a different platform, you can still build the library from source

+

Documentation

@@ -79,19 +94,21 @@ reported and tested.

Samples

-

Sample tests can be found in the sample directory.

+

Sample tests can be found in the sample directory.

F.A.Q.

-

Q. What's wrong with other test frameworks? +

Q. What's wrong with other test frameworks?
A. I worked with CUnit and Check, and I must say that they do their job very well -- the only thing that bugs me is that setting up a test suite from scratch is a pain, it should really be simpler. Most @@ -100,14 +117,10 @@ A. I worked with CUnit and Check, and I must say that they do their job main, manually register suites, then tests. Criterion tries to fix these shortcomings.

-

Q. Where has this been tested? +

Q. Where has this been tested?
A. Currently, on Linux 2.6.32 and Linux 3.15.7, although it should work on - most *nix systems. More tests will be added on the build matrix.

- -

Q. Will this work under Windows/MSVC? -A. Windows support with MinGW/MSVC is coming, but MSVC is a bit of a lost cause - to compile the library itself: the project internally uses c99 features and gnu - extensions.

+ most *nix systems; Mac OS X Yosemite 10.10, FreeBSD 10.0, and finally + Windows 7 (with the MinGW and Cygwin ports of GCC).

@@ -118,7 +131,7 @@ A. Windows support with MinGW/MSVC is coming, but MSVC is a bit of a lost cause
- This page generated using GitHub Pages
theme by Jon Rohan + This page generated using GitHub Pages
theme by Jon Rohan
diff --git a/params.json b/params.json index b08655b..b8603be 100644 --- a/params.json +++ b/params.json @@ -1 +1 @@ -{"name":"Criterion","tagline":"A KISS, non-intrusive C test framework","body":"\r\nCriterion\r\n=========\r\n\r\n[![Build Status](https://travis-ci.org/Snaipe/Criterion.svg?branch=master)](https://travis-ci.org/Snaipe/Criterion)\r\n[![Coverage Status](https://coveralls.io/repos/Snaipe/Criterion/badge.svg?branch=master)](https://coveralls.io/r/Snaipe/Criterion?branch=master)\r\n[![License](https://img.shields.io/badge/license-MIT-blue.svg?style=flat)](https://github.com/Snaipe/Criterion/blob/master/LICENSE)\r\n[![Version](https://img.shields.io/github/tag/Snaipe/Criterion.svg?label=version&style=flat)](https://github.com/Snaipe/Criterion/releases)\r\n\r\nA dead-simple, yet extensible, C test framework.\r\n\r\n![Screencast](https://raw.githubusercontent.com/Snaipe/Criterion/bleeding/doc/screencast.gif)\r\n\r\n## Philosophy\r\n\r\nMost test frameworks for C require a lot of boilerplate code to\r\nset up tests and test suites -- you need to create a main,\r\nthen register new test suites, then register the tests within\r\nthese suits, and finally call the right functions.\r\n\r\nThis gives the user great control, at the unfortunate cost of simplicity.\r\n\r\nCriterion follows the KISS principle, while keeping the control\r\nthe user would have with other frameworks:\r\n\r\n* Tests are automatically registered when declared.\r\n* A default entry point is provided, no need to declare a main\r\n unless you want to do special handling.\r\n* Test are isolated in their own process, crashes and signals can be\r\n reported and tested.\r\n* Progress and statistics can be followed in real time with report hooks.\r\n\r\n## Documentation\r\n\r\nAn online documentation is available on [ReadTheDocs][online-docs]\r\n([PDF][pdf-docs] | [Zip][zip-docs] | [Epub][epub-docs])\r\n\r\n## Samples\r\n\r\nSample tests can be found in the [sample directory][samples].\r\n\r\n* [A simple test][sample-simple]\r\n* [Using multiple suites][sample-suites]\r\n* [Tests with signals][sample-signal]\r\n* [Using report hooks][sample-report]\r\n\r\n## F.A.Q.\r\n\r\n**Q. What's wrong with other test frameworks?**\r\nA. I worked with CUnit and Check, and I must say that they do their job\r\n very well -- the only thing that bugs me is that setting up a test\r\n suite from scratch is a pain, it should really be simpler. Most\r\n (if not all) high-level languages have test frameworks with automatic\r\n test registration, but all the ones for C require you to set up a\r\n main, manually register suites, then tests. Criterion tries to\r\n fix these shortcomings.\r\n\r\n**Q. Where has this been tested?**\r\nA. Currently, on Linux 2.6.32 and Linux 3.15.7, although it should work on\r\n most \\*nix systems. More tests will be added on the build matrix.\r\n\r\n**Q. Will this work under Windows/MSVC?**\r\nA. Windows support with MinGW/MSVC is coming, but MSVC is a bit of a lost cause\r\n to compile the library itself: the project internally uses c99 features and gnu\r\n extensions.\r\n\r\n[online-docs]: http://criterion.readthedocs.org/\r\n[pdf-docs]: http://readthedocs.org/projects/criterion/downloads/pdf/latest/\r\n[zip-docs]: http://readthedocs.org/projects/criterion/downloads/htmlzip/latest/\r\n[epub-docs]: http://readthedocs.org/projects/criterion/downloads/epub/latest/\r\n\r\n[samples]: https://github.com/Snaipe/Criterion/tree/master/samples\r\n[sample-simple]: https://github.com/Snaipe/Criterion/blob/master/samples/simple.c\r\n[sample-suites]: https://github.com/Snaipe/Criterion/blob/master/samples/suites.c\r\n[sample-signal]: https://github.com/Snaipe/Criterion/blob/master/samples/signal.c\r\n[sample-report]: https://github.com/Snaipe/Criterion/blob/master/samples/report.c\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."} \ No newline at end of file +{"name":"Criterion","tagline":"A KISS, non-intrusive C test framework","body":"\r\nCriterion\r\n=========\r\n\r\n[![Build Status](https://travis-ci.org/Snaipe/Criterion.svg?branch=master)](https://travis-ci.org/Snaipe/Criterion) \r\n[![Coverage Status](https://coveralls.io/repos/Snaipe/Criterion/badge.svg?branch=master)](https://coveralls.io/r/Snaipe/Criterion?branch=master) \r\n[![License](https://img.shields.io/badge/license-MIT-blue.svg?style=flat)](https://github.com/Snaipe/Criterion/blob/master/LICENSE) \r\n[![Version](https://img.shields.io/github/tag/Snaipe/Criterion.svg?label=version&style=flat)](https://github.com/Snaipe/Criterion/releases) \r\n\r\nA dead-simple, yet extensible, C unit testing framework.\r\n\r\n![Screencast](https://raw.githubusercontent.com/Snaipe/Criterion/bleeding/doc/screencast.gif)\r\n\r\n## Philosophy\r\n\r\nMost test frameworks for C require a lot of boilerplate code to\r\nset up tests and test suites -- you need to create a main,\r\nthen register new test suites, then register the tests within\r\nthese suits, and finally call the right functions.\r\n\r\nThis gives the user great control, at the unfortunate cost of simplicity.\r\n\r\nCriterion follows the KISS principle, while keeping the control\r\nthe user would have with other frameworks:\r\n\r\n* [x] Tests are automatically registered when declared.\r\n* [x] Implements a xUnit framework structure.\r\n* [x] A default entry point is provided, no need to declare a main\r\n unless you want to do special handling.\r\n* [x] Test are isolated in their own process, crashes and signals can be\r\n reported and tested.\r\n* [x] Progress and statistics can be followed in real time with report hooks.\r\n* [x] TAP output format can be enabled with an option.\r\n* [x] Runs on Linux, FreeBSD, Mac OS X, and Windows (Compiles only with MinGW or Cygwin).\r\n\r\n## Downloads\r\n\r\n* [Linux (x86_64)](https://github.com/Snaipe/Criterion/releases/download/v1.1.0/criterion-1.1.0-linux-x86_64.tar.bz2)\r\n* [OS X (x86_64)](https://github.com/Snaipe/Criterion/releases/download/v1.1.0/criterion-1.1.0-osx-x86_64.tar.bz2)\r\n* [Windows (x86_64)](https://github.com/Snaipe/Criterion/releases/download/v1.1.0/criterion-1.1.0-win-x86_64.tar.bz2)\r\n* [FreeBSD (x86_64)](https://github.com/Snaipe/Criterion/releases/download/v1.1.0/criterion-1.1.0-freebsd-x86_64.tar.bz2)\r\n\r\nIf you have a different platform, you can still [build the library from source](http://criterion.readthedocs.org/en/latest/setup.html#installation)\r\n\r\n## Documentation\r\n\r\nAn online documentation is available on [ReadTheDocs][online-docs]\r\n([PDF][pdf-docs] | [Zip][zip-docs] | [Epub][epub-docs])\r\n\r\n## Samples\r\n\r\nSample tests can be found in the [sample directory][samples].\r\n\r\n* [A simple test][sample-simple]\r\n* [Using multiple suites][sample-suites]\r\n* [Writing assertions][sample-asserts]\r\n* [Adding test fixtures][sample-fixtures]\r\n* [Tests with signals][sample-signal]\r\n* [Using report hooks][sample-report]\r\n\r\n## F.A.Q.\r\n\r\n**Q. What's wrong with other test frameworks?** \r\nA. I worked with CUnit and Check, and I must say that they do their job\r\n very well -- the only thing that bugs me is that setting up a test\r\n suite from scratch is a pain, it should really be simpler. Most\r\n (if not all) high-level languages have test frameworks with automatic\r\n test registration, but all the ones for C require you to set up a\r\n main, manually register suites, then tests. Criterion tries to\r\n fix these shortcomings.\r\n\r\n**Q. Where has this been tested?** \r\nA. Currently, on Linux 2.6.32 and Linux 3.15.7, although it should work on\r\n most \\*nix systems; Mac OS X Yosemite 10.10, FreeBSD 10.0, and finally\r\n Windows 7 (with the MinGW and Cygwin ports of GCC).\r\n\r\n[online-docs]: http://criterion.readthedocs.org/\r\n[pdf-docs]: http://readthedocs.org/projects/criterion/downloads/pdf/latest/\r\n[zip-docs]: http://readthedocs.org/projects/criterion/downloads/htmlzip/latest/\r\n[epub-docs]: http://readthedocs.org/projects/criterion/downloads/epub/latest/\r\n\r\n[samples]: https://github.com/Snaipe/Criterion/tree/bleeding/samples/\r\n[sample-simple]: https://github.com/Snaipe/Criterion/blob/bleeding/samples/simple.c\r\n[sample-suites]: https://github.com/Snaipe/Criterion/blob/bleeding/samples/suites.c\r\n[sample-asserts]: https://github.com/Snaipe/Criterion/blob/bleeding/samples/asserts.c\r\n[sample-fixtures]: https://github.com/Snaipe/Criterion/blob/bleeding/samples/fixtures.c\r\n[sample-signal]: https://github.com/Snaipe/Criterion/blob/bleeding/samples/signal.c\r\n[sample-report]: https://github.com/Snaipe/Criterion/blob/bleeding/samples/report.c\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."} \ No newline at end of file