Fixes #4614 Remove VisualPHPUnit from the codebase, since we don't use the tool anymore (everyone using PHPUnit in command line)

1 files changed, 4 insertions, 45 deletions

diff --git a/tests/PHPUnit/Benchmarks/README.md b/tests/PHPUnit/Benchmarks/README.md
index 6560594cd6..ce750f6918 100644
--- a/tests/PHPUnit/Benchmarks/README.md
+++ b/tests/PHPUnit/Benchmarks/README.md
@@ -1,6 +1,6 @@
 # Benchmark tests
 
-Piwik comes with a system that can be used to benchmark certain Piwik processes. The benchmarking system relies both on PHPUnit and VisualPHPUnit.
+Piwik comes with a system that can be used to benchmark certain Piwik processes. The benchmarking system relies both on PHPUnit.
 
 ##  Benchmarks & Fixtures 
 
@@ -12,45 +12,7 @@ For example, you can test how long it takes to generate reports for one site wit
 in one day, or you can test how long it takes to generate reports for 1,000 sites w/ 12 visits
 each on one day, simply by changing the fixture.
 
-##  Running Benchmarks 
-
-To run a benchmark, first load VisualPHPUnit by pointing your browser to:
-
-http://path/to/piwik/trunk/tests/lib/visualphpunit/
-
-  * On the left you will see a list of files and directories. Click on the 'Benchmarks' directory
-    to expand it. Then click on the 'Fixtures' directory to expand it.
-
-  * Click one of the benchmarks to run (see the next section for a list of benchmarks).
-
-  * Below the file listing is a section with the title 'GLOBALS'. In order to run a benchmark,
-    you'll have to enter some information here.
-
-  * Enter 'PIWIK_BENCHMARK_FIXTURE' in the left input. In the right input, pick one of the fixtures
-    in the 'Fixtures' folder and enter it (w/o the .php extension). For example, you can enter
-    'SqlDump' or 'ThousandSitesTwelveVisitsEachOneDay' (see the next section for a list of fixtures).
-
-  * Click the 'Add' link in the 'GLOBALS' section. In the new row enter 'PIWIK_BENCHMARK_DATABASE'
-    in the left input. On the right enter the name of a new database. This database will be created
-    and saved so you don't have to re-setup the database next time you run a benchmark. If you
-    plan on running the benchmark more than once, this can save a lot of time.
-
-    NOTE: This option isn't required.
-
-  * Now, click the 'Run Tests' link at the top of the page. This will run the test, which can take
-    a long time based on how fast your machine is. When the test finishes, you'll see the following
-    statistics:
-
-    * Total Elapsed Time - the amount of time it took to run the test + setup the fixture + process
-                           PHPUnit's result + etc.
-    * Total Execution Time - the amount of time it took to run the test (this is an important
-                             metric).
-    * Peak Memory Use - The peak memory use for the test (this is an important metric).
-    * Total Memory Delta - The memory delta of every test run, summed up.
-
-NOTE: You cannot at present run more than one benchmark, so make sure you only select one.
-
-##  Included Benchmarks and Fixtures 
+##  Included Benchmarks and Fixtures
 
 These are the benchmarks currently written for Piwik:
 
@@ -88,12 +50,9 @@ To do this, make sure you put your changes into a new git branch. You can create
 branch by running:
     $ git checkout -b branch_name
 
-Run a benchmark using the branch without changes ('master'). Load VisualPHPUnit in a new
-tab and switch branches to the new branch. You can switch branches by running:
-    $ git checkout branch_name
+Run a benchmark using the branch without changes ('master').
 
-In the new tab run the benchmark again. You can now compare how long it took to run the
-test w/o your changes and with your changes.
+Then compare both benchmarks.
 
 NOTE:
   - You don't need git to do this, but it's much easier w/ git.