I’m currently creating rspec test cases for a Rails 2.3 application. The problem I’m confronting is that the application has a dependency on data from an external database like this:
-
Main_User is an external application.
-
Node_User is the application I’m testing.
When a new Node_User is created, Node_User calls Main_User which creates a user and returns with some data which Node_User uses to create a the Node_User.
Is there any way I can query the Main_User database to verify that the record created there contains the data that is passed to Node_User? Or is there a better way to test this?
Thank you!
Yes, you can theoretically query the remote database if you have access to the user/pass/hostname for that database. (Search for “Rails multiple databases.”)
But I wouldn’t necessarily recommend taking that approach. Your tests would be modifying the state of the remote database. This strikes me as unsafe. You’ll be creating bogus records–and possibly deleting or corrupting data, if your tests do any mass deletes or exercise broken functionality. In other words, your tests may do bad things to a production database.
Therefore, I would recommend mocking the remote database in some way. One option would be VCR. It’s really cool, but it would require you to operate on the remote database at least once, because it has to record the first run. Another option is to use one of the tools underlying VCR, such as FakeWeb.
Of course, this only tests the Node_User side of things. You said you also need to verify that the remote record is correct. To do that, I would recommend writing tests on the Main_User side. Such tests would simulate an incoming RESTful request from Node_User and verify the correct result.
That only works if Main_User is your application. If it’s a third-party service, then there may not be a safe way to test it. You may just have to trust its correctness.