3
5 Comments

I recorded an early product tour - Tell me what you think!

Hello everybody,

I just finished uploading an early product tour screencast of Testkit.

There's still a lot to do, the roadmap is huge, but I wanted to give people a general idea of how Testkit will work.

I'd be happy to hear your feedback! Would you use such a tool? What's your current solution? And do you have any must-have features I should implement?

Check out the video here and tell me what you think: https://youtu.be/vkEtmbOL8JQ

P.S. This is also my very first screencast and YouTube video, so I'd be happy to hear some feedback about that too! And yes, I will get a proper microphone next time 😃

posted to Icon for group Ideas and Validation
Ideas and Validation
on March 28, 2021
  1. 1

    not bad!

    it took ~41 seconds for you to actually start the demo... maybe you should try to get in faster?

  2. 1

    I'd say there should be a shortcut to set all screenshots as baseline! Small things like that stretch the video unnecessarily and it shows where some UI refinement could help.

    I also think that only considering "authentication steps" as a prerequisite won't be enough to test large applications with many possible navigation branches; you should consider generalizing this concept.

    The diff tool seems to be very helpful but, depending on the amount of changes, it's probably also a bit too detailed for that small preview. I'd love to have some separate detail view with a drill down on what exactly has changed.

    All in all, the tool seems to be really useful and once a headless CI version exists, too, it would be a pretty complete suite! Well done! 👏

    I'd actually love to have a similar recording extension to generate TestCafe or Cypress tests! Does that exist?! Maybe this could be an interesting hook for you: "Look, I have generated this JavaScript for you, now if you want a full suite, go to Testkit.app!"

    1. 1

      Hey, thanks a lot for your solid feedback! The "Set all baselines" shortcut is a good idea for sure! I planned to also support setting authentication data with a custom preflight request that the user can set up - Is that what you were thinking of, or do you think there is need for more than just these two authentication methods?

      About the diff tool, I'm honestly not happy about the current UI as well, and will focus on that sometime soon, but first I want to handle all the complicated test scenarios (Such as file uploads, Drag & Drop etc.)

      Thanks a lot for your recommendations, will definitely look into them! 🙏😃

      1. 1

        Is that what you were thinking of, or do you think there is need for more than just these two authentication methods?

        No, I meant to generalize the concept of a "prerequisite" in general, no matter whether it's a login or some other tedious steps before you get to the point that you actually want to test.

        Imagine you want to test a tool where you need to setup tons of stuff first before you get to a point where you need to test all possible branches. Recording these tons of stuff only once (just like login) would ease the later steps.

        1. 1

          Ah, now I understand! Basically to be able to prepend or append any test, not just authentication! That makes a lot of sense of course, thanks a lot!!

Trending on Indie Hackers
From building client websites to launching my own SaaS — and why I stopped trusting GA4! User Avatar 37 comments The “Open → Do → Close” rule changed how I build tools User Avatar 27 comments I lost €50K to non-paying clients... so I built an AI contract tool. Now at 300 users, 0 MRR. User Avatar 21 comments Everyone is Using AI for Vibe Coding, but What You Really Need is Vibe UX User Avatar 20 comments Learning Rails at 48: Three Weeks from Product Owner to Solo Founder User Avatar 19 comments If you are About to Quit, Read This. User Avatar 10 comments