Michael Whatcott

icon indicating a website link https://michaelwhatcott.com

icon location Disciplined Development of Successful Software through Collaborative Crafting

Results 48 comments of Michael Whatcott

Example of how to handle an exception

@jruere - It's been a while since I've worked on this project. Can you paste in an example of what you're trying to accomplish?

Example of how to handle an exception

You can assert that an assertion was raised: ``` this(function_that_raises_exception).should.raise_an(Exception) ``` https://github.com/mdwhatcott/pyspecs/blob/master/tests/test_should.py#L108 Conversely, you should be able to chain `.NOT` to get the inverse effect: ``` this(function_that_finishes_successfully).should.NOT.raise_an(Exception) ``` https://github.com/mdwhatcott/pyspecs/blob/master/tests/test_should.py#L20

Example of how to handle an exception

Yes, if the function receives arguments, wrap it in a lambda or a separate niladic function. I'm not doing very much python work right now, other than quick scripts that...

Example of how to handle an exception

You're welcome. Glad you are finding this project useful.

"let" around multiple specs causes only last spec to execute

Resolved by #164

module declares its path as: github.com/smarty/assertions but was required as: github.com/smartystreets/assertions

You'll need to update goconvey to the latest version (1.8.0), which requires the assertions module at the new location. `go get -u github.com/smartystreets/goconvey`

Update ShouldNotEqual and ShouldNotBeNil to not rely on its counterpart

@ale7714 - thanks for submitting this pull request. Will you go into more detail about what problem are you trying to solve?

Update ShouldNotEqual and ShouldNotBeNil to not rely on its counterpart

@ale7714 - Ah, interesting. I anxiously await any results you can share from your investigation.