What are the testing strategies used in the project?

[RR2M4A]

Hi, I’m getting started with contributing to the project and would like to better understand the testing methodology. From what I’ve seen, you currently use:

Unit tests
Snapshot tests for data regression
E2E Testing

I came across this discussion from 2023 regarding tests. I’ve reviewed it, but I’m curious whether there have been any updates or changes to the testing strategy since then. Specifically, I’m interested in:

Acceptance tests
Performance/load tests for the parsers
Security tests

Is there any internal documentation or guidelines regarding these types of tests, or any planned strategy for them? What are the testing metrics? Also, is there a section where I can find information about both functional and non-functional requirements of the project?

Thank you very much for your help!

[VIKTORVAV99]

Hi!

Not sure what you mean by acceptance tests but there is no test suite for performance, when needed these have been made on a case by case basis in benchmarking scripts locally.

For security we run CodeQL on the entire codebase.

[RR2M4A]

Oh, I see, thanks for clarifying.

By "acceptance tests" I meant if before each release they are validated by a client or by the developers themselves.
And regarding performance benchmarks, are those scripts available somewhere in the repo for contributors to run, or are they mostly local?

[VIKTORVAV99]

The performance scripts are run locally and in many cases never saved long term.

All deployments go though or internal CI which runs integration tests and requires a manual approval from a developer before being deployed.

[RR2M4A]

I see, thank you for the answer!