I'm a passionate COO dedicated to helping my clients craft state-of-the-art software solutions. With over 15 years in the industry, I've evolved from coder to tech leader, gaining hands-on experience in building various platforms and leading teams of many developers. This journey has empowered me to mentor emerging leaders and share insights on team-building, successful project management, and outsourcing. In the dynamic realm of tech, I'm committed to shaping the future and inspiring others to push boundaries alongside me.
Thanks to a good combination of RSpec and Kameleon, we have managed to write an expressive end-to-end test as well as six supportive tests in no time at all.
In the last article we added a few GraphQL mutations to our test application. It is time to create automated tests for each of them. But first things first, we need to set up `RSpec` in order to write better specs.
Today we are going to add specs (again, we will focus only on the happy paths) for GraphQL queries. But there is one thing about the current implementation of the queries that I don’t like. We have everything defined in one file: `app/graphql/types/query_type.rb`
In this article, I would like to focus on adding GraphQL mutations. We will be working on the test application we created previously in this article. It might be helpful for you to know the structure, models, and types we are using so I encourage you to take a look.
The choice of benchmarking tools is often a compromise between a number of factors such as: ease of use, features, and time needed to prepare and maintain a test suite.
A few techniques which can help you handle errors in production if your client is non-technical. You should always apply best practices in your projects to avoid bad situations. But if some errors slip through your test suite, code reviews, QA and testing on staging, be sure that you handle it in a proper way.
Sep 17, 2020 ・7 min read
SaaS Founder Starter Academy
Everything you need to know to successfully launch your SaaS app.
