jam510

6 ms·

1. 1.▲
   Script that emails you transcript when your mentioned in a meeting(github.com)

   2 points by jam510 10y ago|0 comments
2. 2.▲
   Testing NSURLSession with Swift (and UI Testing)(masilotti.com)

   1 points by jam510 11y ago|0 comments
3. 3.▲
   UI Testing Cheat Sheet for iOS(github.com)

   1 points by jam510 11y ago|0 comments
4. 4.▲
   Three Ways UI Testing Just Made Test-Driven Development Even Better(masilotti.com)

   3 points by jam510 11y ago|0 comments
5. 5.▲
   Better Dependency Injection on iOS(masilotti.com)

   1 points by jam510 11y ago|0 comments
6. 6.▲
   UI Testing documentation now available online (unofficial)(joemasilotti.github.io)

   1 points by jam510 11y ago|0 comments
7. 7.▲
   by jam510 11y ago

   Totally agree with you there. I try to have a few levels of testing: - Unit - everything is mocked but the object under test - Integration - common flows are worked through in code (eg. showing populated cells from a fixture JSON file) - Fe
8. 8.▲
   by jam510 11y ago

   Author here! Happy to answer any questions here or in the comment section of the post.
9. 9.▲
   by jam510 11y ago

   I agree; of the third party libraries KIF was the nicest to work with. The biggest issue is that it doesn't run reliably enough. When we moved our code to our CI box tests would false-negative almost 25% of the time. I tried ticking th