eql | an easy jdbc sql framework of an alternative to ibatis | SQL Database library

Your mocking expectations should happen in the test before the code is calling them, so

Have you tried using template laterals?

It's because you don't have a file parameter.

So your check_file is using this part:

There's no need to reopen a Tempfile, it's already open and delegates to File.

You have defined post with let! which shadows the post method for sending request. Come up with another name for it.

The loop executes a lot faster than the Cypress commands or the zoom operation, you can see it if you add a console.log() just inside the loop

Your code seems to be doing exactly what you want it to do.

You used a technique called polling. It has its issues, like performance and rate limits which you need to consider. But you can't really not use a loop in this case. Because that what polling essentially is.

You could maybe use some async scheduler (like sidekiq) and after each http request you could schedule another one in the future. Or you could use something like sidekiq-cron gem. In that way you can avoid using a loop.

If you want to avoid making requests even when nothing changed on the server you'll need to use some websockets or so called long polling. But idk if the api you to talk to supports it.

Alternatively the api could create a webhook and the api would call you when there is a change.

Assertion libraries (like chai) have functions like expect and assert that will throw exceptions when the condition they are checking for fails. A test runner (mocha in this case) can use this fact to detect test failures by executing the test case within a try/catch block. If an exception is thrown by the test case (i.e., by the assertion library), the test is deemed to have failed.

If you look at mocha's documentation, for example, you will see that:

Mocha allows you to use any assertion library you wish...generally, if it throws an Error, it will work!

So in pseudocode, mocha is doing something like:

To be able to build the project with react-native-maps and use_frameworks as described in the question I had to fork the react-native-maps library and replace

Google-Maps-iOS-Utils with Google_Maps_iOS_Utils in header imports in

lib/ios/AirGoogleMaps/AIRGoogleMap.m: