PHPackages                             fp/testo - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. fp/testo

ActiveLibrary

fp/testo
========

Extract test as example and put them to doc

41.3k2PHP

Since Oct 11Pushed 12y ago14 watchersCompare

[ Source](https://github.com/formapro/testo)[ Packagist](https://packagist.org/packages/fp/testo)[ RSS](/packages/fp-testo/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

Testo [![Build Status](https://camo.githubusercontent.com/f50f49255c3770f1a45e2e24e3c0fd96f249dde07e5e6228edbe6eefff9b1bb9/68747470733a2f2f7365637572652e7472617669732d63692e6f72672f666f726d6170726f2f746573746f2e706e673f6272616e63683d6d6173746572)](http://travis-ci.org/formapro/testo)
============================================================================================================================================================================================================================================================================================

[](#testo-)

Do you remember those outdated examples in a documentation?.

Or times while updating documents you had to test examples manually?

This days in the past. Testo come into play.

Example
=======

[](#example)

Let's say you have a `README.md`:

```
@testo examples/Testo/Examples/README.md {
Some description of the awesome code:

@testo 35a8d2d426c05614551484dcdd450f37 }

```

and there is a class:

```
// @testo Testo\Examples\Hello {
// @testo }
```

So after you run `Testo` there will be clean `README.md`:

```
@testo examples/Testo/Examples/README.md.expected {
Some description of the awesome code:

@testo 35a8d2d426c05614551484dcdd450f37 }

```

What's inside?
==============

[](#whats-inside)

```