top of page

FAQ:

(Q) Are there any limitations or nuances in using testhelper that you should know in advance?

(A) Testhelper is designed to facilitate test automation and solve common testing problems, so:

  • It is recommended to use it in a test Docker environment: raise a project, services (databases, brokers, etc.) in docker containers in the GitLab (or analogues) pipeline or locally (more for debugging and writing autotests), when using real services, problems are possible (the tool will not meet the timeout of responses, consumers, etc.).

  • Testhelper designed to run tests in one thread, which is due to both stability and follows the principle “clean everything before each test”, of course, you don’t have to resort to cleaning and you can use generated data, but stability is not guaranteed when running tests in multiple threads. If you have a lot of tests and their execution time is longer than acceptable, it is recommended to parallel the execution of different jobs in the pipeline (this ensures complete isolation).

(Q) Can I use this testhelper in my commercial or non-commercial projects?

(A) Yes. It is highly desirable to share your experience and suggestions.

(Q) Stability or performance?

(A) Definitely stability.

(Q) Can I use testhelper to test the backend in another programming language?

(A) Yes. Roughly speaking, the application from the outside works the same in any language. But this does not coincide slightly with the standard (for me) principle of test automation: autotest language = application language.

INFO

IN progress

Info

in progress

INFO

In progress

© 2025 BUGREAPER

bottom of page