Question: i extract som html information of a website using file\_get\_contents and i want ti print by echo

how i can do 

```
$page = file_get_contents('*******');
preg_match("/<span class=\"a-text-strike\".*span>/", $page, $precio_antes);
preg_match("/<span id=\"priceblock_ourprice\".*span>/", $page, $precio_ahora);
preg_match("/<td class=\"a-span12 a-color-price a-size-base\".*td>/", $page, $precio_descuento);

echo "Antes: ".$precio_antes. "Ahora: " .$precio_ahora." (-" .$precio_descuento. "%)";

```

Answer: 
Extending on [Merlin's answer](https://stackoverflow.com/a/38422707/1069189), here is how I've implemented publishing jest test results AND code coverage to TFS2015 vNext builds (I am using create-react-app boilerplate):

First install required packages on the Server you are running your Agent on:

npm install -g jest-json-to-tap

npm install -g tap-xunit

1. configure jest to output json, by changing in package.json the "test" task to:
"test": "react-scripts test --env=jsdom --json",
2. configure jest options in package.json:
"jest": { "coverageReporters": ["cobertura"] }
3. created a vNext build (TFS2015v4) with the following tasks:

a. "npm" task, command=run, arguments=test -- --coverage | jest-json-to-tap | tap-xunit > TEST-result.xml

b. "publish test results" task, format=JUnit

c. "public code coverage results" task, code coverage tool=Cobertura, Summary file=$(Build.Repository.LocalPath)\coverage\cobertura-coverage.xml

4. make sure your build's "Variables" include setting the environment variable "CI"="true"

NOTES:
- test results will not include times nor assemblies - something to extend for the future...

Voila'! Running this build will correctly publish the test results and code coverage stats, as well as report artifacts.
I'm not sure about jest, but there's a neat npm package that can convert TAP based results to xUnit XMLformat, and then you can publish that to TFS.

Take a look at [tap-xunit](https://www.npmjs.com/package/tap-xunit).

I had a build environment where javascript testing was done by various tools and frameworks (AVA, Mocha, Jasmine etc). We decided to export them all to TAP format, run them throw tap-xunit and then publish to TFS.

Basically, you need something like this:

```
npm test | tap-xunit > results.xml

```

You pipe the results to tap-xunit and save them to an XML. This gives you an XML formatted as xUnit that you can publish to TFS. If you're running TFS 2015, I strongly recommend going with vNext builds, a lot easier to get these running. Check the "Publish Test Results" build step.