6 Commits

Author	SHA1	Message	Date
Ed Morley	7a579e4eb7	Make assertCapturedSuccess display stdout if stderr was empty (#390) ... In cases where there is no stderr there was previously no output, which made it hard to find the cause. The assertion messages have also been adjusted to remove the repetition (shunit2 already outputs expected vs actual itself). Before: ``` testPipenv ASSERT:Expected captured exit code to be 0; was <2> expected:<0> but was:<2> testPipenvVersion ``` After: ``` testPipenv ASSERT:Captured exit code - expected:<0> but was:<2> ! Warning: Your application is missing a Procfile. This file tells Heroku how to run your application. ! Learn more: https://devcenter.heroku.com/articles/procfile -----> Installing python-2.7.13 -----> Installing pip -----> Generating 'requirements.txt' with pipenv testPipenvVersion ``` Fixes #389.	2017-05-25 11:46:09 -07:00
kennethreitz	c3849fb6d3	improvements	2017-03-14 13:36:14 -04:00
kennethreitz	e9108858fc	v100	2017-03-14 11:59:39 -04:00
kennethreitz	63810f29d3	passing tests	2017-03-10 11:43:11 -05:00
kennethreitz	012cb8a4df	Added more tests	2017-02-01 15:09:49 -05:00
kennethreitz	cd52da6155	tell travis to run the tests	2017-01-24 23:16:36 -05:00