No description provided.
adding dynamic methods to tests explicitly to fix inconsistently fail…
asgard-pull-requests #9 SUCCESS
This pull request looks good
Why not put these calls in setup()?
Just because it's not needed (or wanted for all tests in the class). I guess it doesn't do anything as time consuming as parsing JSON files (today), but I still wanted to separate the methods that require it. A longer term fix would be to remove all Mocks calls from each method. The ones that can't be remove are integration tests that belong in the test environment. At that point I wouldn't have an issue with using Mocks methods in setup().