Sentry example
A Test Study of Sentry with the help of Concordant. 21st March 2025
Last updated
A Test Study of Sentry with the help of Concordant. 21st March 2025
Last updated
Come up with a test.plan.json
within a couple of hours as if opening up an unknown legacy code base.
test.plan.json
configuration:State
Concordant 1.0.0
Sentry codebase state in March 2025
Macbook Air M3
Result On a Macbook Air M3 the example configurations runs a full reload in about 10s. Without configuration from 30s-60s depending on the amount of effects in the codebase. In general, smaller changesets run faster.
Memory usage varies between 1GB-10GB depending on the amount of components extracted and activated by effects.
At the time of the latest benchmark, the example configuration produced nearly 700 components, and a run without a configuration produced nearly 7000 components.
Time
10s
30s-60s
Memory
1GB
10GB
Components
700
7000
Dependencies
52 000
52 000
Concordant v1.0.0
Test Rounds using file names as the test case name become cumbersome with the path/to/route/index.ts
architecture. => An option to switch between file path and file name would be helpful in separating multiple files with the same name at a glance
Concordant does not support Python yet, which means only the frontend can be analysed => Python support would be mighty helpful
Test Automation is not fully recognised by default => Improve configuration
Sentry
No feedback yet.