Find yourself manually testing your app E2E repeatedly?
Possibly a B2B/Enterprise use case but thought to float it here.
How painful is End to End (E2E) testing for you? Please share your stories below. 😊
For context, I've worked on a handful of B2B/Enterprise apps and, while End to End (E2E) testing is a necessity, it takes valuable time from the engineer's schedule. Of course, one solution is to hire a QA engineer (or team). But not all product teams have this luxury. So, E2E testing inevitably falls on the engineer's shoulders. This is not to say it shouldn't be, but the repetitive nature of E2E testing deserves to be automated! I'm considering a solution in this area (already have a prototype on the way), would welcome your thoughts.
Trending on Indie Hackers
Protect your momentum like your life depends on It
We are live on Product Hunt
Don't be a Jerk. Use this Tip Calculator.
Opsgenie vs. Splunk: Choosing the Right Incident Management Solution
Definitely check out https://www.cypress.io/
Indeed, I've tried Cypress before and it looks very promising. It was part of the motivation behind this idea. 🙂 Out of interest, what do you think of the ability to create E2E tests without code? Just record actions, set assertions and you're good to go
Hello, hope it's relevant info – right now I am looking for a proper solution for E2E testing. Currently, I do testing personally as a product owner. It is time-consuming and sometimes I just have to skip the testing (which is not a good idea at all). But it's still better to burn my time than the time of developers.
I decided to outsource it at first – to find some time to set up an automated solution. But, I am looking for a tool that would let me create a test with both code and no-code and would integrate with GitLab.
The "final" solution would be a combination of human and automated tests. Automated tests would test user stories that don't change often (I am afraid of setting up a test and having to change it often). Humans will do test in case of new features or changed workflows.
There's one more interesting thing that saves my time – the instructions for testing (usually a combination of several user stories) are almost the same for both creating automated test and manual testing. It is also very similar to scripts for user experience testing.
Does anyone have a suggestion or ideas?
Thanks!
P.S.: Here's my current list for tools for E2E testing: https://www.notion.so/uncool/dd01f88b957e44e68e53707286252c29?v=27195af62ee14cf3b6d44c4ea4bae113
Wow, thanks Honza for your very thorough answer! 😊
I feel you. I've worked with PMs, Customer Success who shouldered this burden.
This is something I've spent some time thinking about too. They're very algorithmic. The only difference may be explicit vs implicit: humans are able to infer e.g. UX issues while manually testing, so there's definitely benefit in manual testing, as you say.
I'm going to check out your list of tools. If you have time to learn tools like Cypress, I would recommend it but of course it may be a long learning curve (to get the setup right). @Bsme mentioned in the comments about a tool called Checkly that may be worth evaluating too. Short of that, I'm doing this bit of research right now and soon may prototype a new solution based on Cypress (but no code) that I can keep you posted on!
Thanks for the answer – regarding my programming skills, I have some experience with PHP but regarding Javascript, I am a novice. So the learning curve is now very looong.
Definitely keep me posted! ;)
If you don't mind a follow up question @honzapav I'd like to find out more! 🙏
I'm trying out a few of the tools in your Notion doc, and I kept wondering to myself how you evaluated the score (1-10) for each tool. Would be keen to know!
Aside from that, by "Gitlab integration", did you mean "I want to run tests for each PR" or that you want to have ownership of the underlying code in Gitlab? I'm also a Gitlab user, like you. 😊
Of course, np ;).
Regarding the score – this is very subjective. I didn't create it with an intention to share it (but I don't mind sharing it). I have tried to answer the question "How willing am I to choose this tool".
Regarding Gitlab – yes, that's it. We have a quite nice and helpful CD/CI process and I just want to insert E2E test as another step.
Hope it's a bit clearer! Feel free to ask.
Perfect, glad to hear! One final Q for the day while on the topic — which of the different types of testing are most important to you? I'm curious as I've come across a need for user flow most personally but may be different for yourself/others
In the beginning, we bet on integration tests (we still don't have tests for everything). But it is not enough. So E2E tests come handy. We skipped unit tests for now (again, devs' time is limited) as we caught the problems via integration tests.
Hi @logicalicy
This sounds interesting. I am also trying to do something in the testing space but totally not related to this. I am try help DevOps people to do infrastructure testing.
Any how....have you tested the market? How open are people/companies willing to pay for these services? Is it just a nice to have or will they actually pay for something like this?
I'm at the very beginning of my research. 😊 I've yet to find out its viability. What I do know though are these proxies:
Cool, let me know if I can help!
I am. I have worked on teams where this has been a common struggle. It's often leftover to the product owner to perform the testing before it goes to production.
There are a few solutions that do e2e testing automatically with minimal code. My favourite is checklyhq
Thank you, Checkly gets really close to what I'm thinking! What do you think of the ability to create E2E tests without code? (I see Checkly uses Puppeteer)
Yes would be great to do, but I find I always have to tweak the code. Checklyhq(has a no code way to do it) using a chrome extensions you can click and it will spit out the puppeteer code.
But I do think there needs to be more in the space... nothing is great but checklyhq comes close
Going to check out this feature you describe on Checkly, thanks!
Ah thank you, I'll be sure to check it out!
This comment was deleted 5 years ago.
This comment was deleted 5 years ago.
This comment was deleted 5 years ago.
This comment was deleted 2 years ago.
Thanks, will check out!