How to do QC - any best practices?

Questions
1

Hi bubble community!

I’m looking to improve the quality control process for ourBubble app and would love to hear about best practices others are using.

I’m especially interested in:

  • How you write and manage test case descriptions (manual or automated)
  • Automated testing tools or frameworks that integrate well with Bubble
  • Techniques for regression testing and preventing breaking changes
  • Version control strategies that help with QA
  • Any custom logging, error tracking, or performance monitoring setups

If you’ve developed a solid QC system or have tools/methods that work well with Bubble, I’d really appreciate your insights.

(I’m also considering bringing on a part-time QC expert to do our testing, it probably takes ~half a day per week on a flexible basis. If that’s you then send me a DM!.)

Cheers, Koen

2

@rico.trevisan recently posted his experience using Playwright for automated testing.

There is also a no-code tool named Preflight that allow you to set automated e2e tests.

There is a bunch of topics in the forum covering automated testing.

1 Like
3

Thanks for the reference. Another tool that I’ve added to my to-try list: https://www.browserstack.com

1 Like
4

I believe Flusk also does error tracking and it’s sort of built-in to Bubble. I haven’t tried error tracking yet. I remembered it the other day when I was doing some testing. :blush:

5

@J805
Yes you are right. flusk has error tracking (although it has been down since we moved to a dedicated plan >2 months ago). It also reports a lot, so hard to differentiate between all the noise it sends out. At the moment I only use it for identifying the most reported errors and then reactively looking into them if they are bugs.

1 Like
6

Buildprint can generate test plans based on your changes to help identify regressions and edge cases that you should test.

It’s free.

1 Like
7

That makes sense. :blush: