Testing articles by our experts
Testing is a crucial element of a good development process, and here’s why.
By testing your app thoroughly and early, you can make sure your project requirements are sensible and will allow the app to meet users’ expectations. Proper testing can help you avoid technical debt, improve team flexibility, take on a modular approach and reuse code, and more.
So why are good testing processes so rarely implemented?
Test-driven development can be the saving grace of startups and small companies, allowing them to save time and money, and deliver much sleeker apps to users. If your new product is full of bugs, how likely is it that early adopters will stick with it and promote it among friends? Not very. This is why early testing is 100% worth the investment. Find out how to implement it without making the 5 most common testing mistakes.
Recently, we had an interesting request from one of our clients where we needed to implement time travel for testing purposes - or fake time travel at least! The Quality Assurance (QA) team of one of our clients wanted to test functionality under particular time constraints within their application. To do that, they needed is to move the application’s internal clock to check and see whether some these time-based actions were allowed or forbidden (depending on the case). Mocking up operating system’s datetime settings on Heroku was the answer, with setting up environmental variables for datetime testing. Heroku datetime testing in a Ruby on Rails application required a little configuration - but we were able to get the job done.