gnithin / flow-test

A pod to unit-test non-UI flows based on method selectors strings

Hi!

I am Nithin 👋

• 🏢 Software dev @Klaviyo, ex-SDE @Media.net
• ❤️ React and Python
• ⛏️ Worked on projects in Golang, Objective-C, PHP, long long ago
• 📫 Email me @ [email protected]

flow-test's Issues

Arguments assertions as well in the method-specs

There should be another macro similar toKMFMakeMethodSpec which takes in a third argument which is a block. The block will contain the invocation object. That invocation object can be used to fetch the arguments of the current method. It can then be used to assert the values it represents.

Support for Swift

Test this out for swift. It should not cause too many pain-points since XCTestCase is used similarly 🤞 . This would involve building and testing this for various swift versions

Handle repetitions of the methods

There could be times where a method added to the flow-test is called multiple times. Currently, the end-user is expected to add it every single time that method might be called. This should be made a lot easier.

Not sure how I'd perform this

Negative method-specs assertions

Assert that certain methods are not to be called at all! I have no idea if this is a useful feature, but I've encountered circumstances where this could be useful

Support for static classes in method-specs

Support for static classes as well. Not possible right now, since that's not supported in the Aspects lib itself.