Skip to content

Commit

Permalink
WIP
Browse files Browse the repository at this point in the history
  • Loading branch information
michielgerritsen committed Aug 17, 2019
1 parent a7870fc commit 79e58b0
Showing 1 changed file with 14 additions and 2 deletions.
16 changes: 14 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,22 @@
# Revive

Fix your Magento Integration Tests using this tool
Got a Magento 2 store where the integration test always fails with some database errors? You can do an attempt to fix them manually by [following this blogpost](https://www.michiel-gerritsen.com/debugging-the-magento-2-integration-test-setup/), or use this tool. This tried to find the root cause of why your tests are failing and apply a fix for them.

## What's in the name?

We've been all in that place: A shiny new project. You can do everything right this time! But as times goes by and deadlines needs to get meet, testing may not be very high on you priority list. When you finally want to start writing tests it turns out that your test setup is broken.

That's why it's called Revive: It helps you to revive this feeling at the start of the project: You ARE going to do this better this. Heck, you've already got this far that you are trying to run integration tests.

## Usage

You have 2 options:
You have 2 options to use Revive:

- Download `revive.phar` from the [release tab](https://github.com/michielgerritsen/revive/releases).
- Clone this repository and run `composer install`. You can revive then using `php src/revive.php --root-dir=/path/to/your/magento/installation`.

## Testing

You can run the tests using PHPUnit:

`vendor/bin/phpunit`

0 comments on commit 79e58b0

Please sign in to comment.