[DX] Help the user know how to test a migration file #173

Closed
weaverryan opened this Issue Jul 4, 2014 · 3 comments

Comments

Projects
None yet
5 participants
@weaverryan
Contributor

weaverryan commented Jul 4, 2014

Hi guys!

One of the trickiest parts of using migrations are testing them. That's a tough workflow (and sometimes you'll just need to pull a production schema dump to test things).

After running a generation or diff, what about adding a message to tell the user how they could run this migration independently locally to test it:

To run just this migration for testing purposes, you can use migrations:diff --up 2014XXXXXXX

Thoughts in general? Overall, I want to help people into the right migrations workflow - it's tough.

agallou added a commit to agallou/migrations that referenced this issue Jul 5, 2014

Help the user know how to test a migration file
Added a message to explain how to test the migration at the end of the
diff and generate commands :

```
To run just this migration for testing purposes, you can use migrations:execute --up 2014XXXXXXX
```

See #173

@mikeSimonson mikeSimonson modified the milestone: 1.0 Feb 15, 2015

@allan-simon

This comment has been minimized.

Show comment
Hide comment
@allan-simon

allan-simon May 24, 2015

what is the status of this ticket ? As I see it's the only one left for the 1.0 milestone and there's already a PR opened on this

what is the status of this ticket ? As I see it's the only one left for the 1.0 milestone and there's already a PR opened on this

@lcobucci lcobucci removed this from the 1.0 milestone Aug 19, 2017

@lcobucci

This comment has been minimized.

Show comment
Hide comment
@lcobucci

lcobucci Aug 19, 2017

Member

I've remove this from v1.0 because it was already released without this feature. @mikeSimonson what should we do regarding this?

Member

lcobucci commented Aug 19, 2017

I've remove this from v1.0 because it was already released without this feature. @mikeSimonson what should we do regarding this?

@mikeSimonson

This comment has been minimized.

Show comment
Hide comment
@mikeSimonson

mikeSimonson Aug 25, 2017

Member

We should try to improve the documentation in general but also specifically regarding this.

Member

mikeSimonson commented Aug 25, 2017

We should try to improve the documentation in general but also specifically regarding this.

@jwage jwage added this to the 2.0 milestone May 5, 2018

@jwage jwage added the Documentation label May 5, 2018

@jwage jwage closed this May 16, 2018

@jwage jwage removed the Improvement label May 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment