Landing Page
by Nick KarnikAfter trying out several SaaS products for creating landing pages, I put up a page to collect signups @ https://testerbot.io/. I got some help for the copy from Fiverr, but I'm not really satisfied with it. I thought about reaching out to designers but decided to push that out. The MVP is coming along.
-
2
@theoutlander I am a potential user of your product.
I understand the principles, but I'm sure you know that tech people want to know the details of how it works and not just the big picture ;)What do you test, which framework, how does the automation work?
-
2
@Sam_insurgent - Just noticed the first line of your message. I'm excited to hear that you are a potential user!
Could you please share some insights about your use-case? Is it domain-specific?
Is there a specific feature that stands out for you or something that you'd like to see in a product like this?
Thank you!
-
1
I have read countless times "fully automated testing, super flexible, blablabla" which in the end is never fully automated and it's faster to create our own unit tests than thinking how this can fit in a solution, and how to overcome the limitations. Automating unit tests is really hard.
So I don't believe any marketing message. I just want to see how this works. I can see a number of diagnosis checkboxes on your landing page. If you can run a diagnosis similar to Google Page Speed Insights for bugs and SEO, and point out the issues on all browsers that would be really useful. FYI our website is http://cashcoach.io
-
2
Thanks for the insights. I haven't come across products offering an automated way of testing UI's. I'm not sure how anyone can create automated unit-tests. I've thought about it, but it's a set of different problems that I didn't want to get into :D.
Do you see CashCoach using it or did you have another product in mind for automated testing?
-
1
I was considering your testerbot for Cash Coach :)
Do you have already a product in mind or are you just testing ideas on landing page?-
1
I've built the Automation Framework, implemented ~30 test cases, and created a basic UI (minus reporting).
I'm not happy with the UI. I used Shopify Polaris to create it, but I need to switch because I'm finding it limiting. It is one of the best React UI Frameworks I've come across. They've done a fantastic job designing it, but it works best when used to build Shopify apps. I'm thinking of switching over to Bulma this weekend.
I'm struggling with a few pieces at the moment:
-
I need to prioritize the implementation and align it with a release timeline so I can incrementally release it. I don't know which buckets to focus on for the first few releases as all of them are important for a well-tested application and they take quite some time to implement.
-
Automatic Form Testing is one of the most complicated pieces. Especially, creating scenario tests with minimal user interaction so I'm not sure if that's something I should push to the end or experiment with now.
-
Semi-Automatic testing will require users to modify their dev-code. I'm not sure if that's something people will be okay with. However, if they subscribe to this framework that will be one of its core features.
I need to make a good looking UI and release even if it has partial tests. Then I can focus on increasing test coverage, creating reports and other integrations.
I can give you beta access once this is in the cloud. If you want something sooner, I can push an alpha version next week and you can play with it if you have time. Your feedback based on your use-case will help me focus on the right pieces. 🙏
-
1
If that can help you prioritize the implementation, you don't need fancy UI on day1 when building dev tools :)
Any testing requires at some point code refactoring. The key question will be: is it faster to implement unit tests from scratch than reading your doc and implementing it?
Also devs are known to prefer spending a whole weekend trying to hack something rather than paying $10 for a ready to use solution.
-
-
-
-
-
-
1
Thanks for the feedback, @Sam_insurgent! I'm working on improving the content for the landing page. I will address your questions in the next few iterations.
We're looking at bridging the gap between functional testing and rest of the test buckets that often get overlooked due to lack of resources (SEO, Accessibility, Performance, API Tests, Form Tests, Link Checks, Best Practices, Page Speed, etc.). All of this without writing any code. I'm trying to nail the specifics of the automated functional testing as there are a lot of gotchas.
For the first release, I may focus on test buckets outside of functional testing as most people start automating functionality. I'm hoping to support semi-automatic tests that require minimal human interaction and custom coded tests in Javascript.
Thanks for the thoughtful questions!
-
-
2
Need to figure out why people want testing is it really for productivity? I want testing for peace of mind, it might be different for different companies.
- I would have some use cases
- How to section
- FAQ
or you could go the route of a manifesto. People who do testing are normally passionate about it.
Might also want to speak with @rosiesherry I believe she was a co-founder of https://www.ministryoftesting.com/
-
1
That's a good point about productivity. I'm not sold on that part of the tag line either. Similarly, peace of mind is another aspect. The reason definitely differs based on the company as you mentioned. At the end of the day, creating automations with high-coverage takes a long time. Not everyone cares about automation past functional testing so this tool won't work for everyone.
Thanks for the suggestions to add those sections. I thought of expanding the content as I got towards releasing the MVP, but I can start adding some of that sooner.
-
2
What is it that you are not really satisfied with?
-
2
I had made a few modifications to the copy. I'll dive into one of them.
My first tag line was "Automatically Test Your Web Applications."
The copywriter came up with, "Boost Productivity & Skyrocket Efficiency with Automated Website & Web Application Testing." I felt it was a bit long and not as captivating.
Next iteration it was changed to, "Skyrocket Efficiency with Automated Web Application Testing."
Finally, I changed it to, "Boost Productivity with Automated Web Application Testing". I'm not a huge fan of this. One element that I'm contemplating is the use of Automatic vs. Automated. IMO, the latter is used when users create the automations vs. a tool that just does it for you.
-
