recheck
recheck copied to clipboard
retest
Replace traditional assertions with a single check.
It's since kryo 5 it's for good reasons the default to register classes, for more details see https://github.com/EsotericSoftware/kryo/issues/398 In KryoPersistence.java#81 remove the line and add registration for all used classes.
*Before submission, please check that ...* - [x] this is related specifically to recheck and not its extension (e.g. [recheck-web](https://github.com/retest/recheck-web)). - [x] the [documentation](https://docs.retest.de/) does not mention a fix (e.g....
Consider the following change: Adapted HTML (removes `id` attribute completely): https://github.com/retest/recheck-web/pull/297/files#diff-b980e03c12cee358e1072d97aedd8dedR165 Our GM after apply via review: https://github.com/retest/recheck-web/pull/297/files#diff-b980e03c12cee358e1072d97aedd8dedR165 As can be seen, the XML element for the `id` attribute is...
*Before submission, please check that ...* - [x] this is related specifically to recheck and not its extension (e.g. [recheck-web](https://github.com/retest/recheck-web)). - [x] the [documentation](https://docs.retest.de/) does not mention a similar solution...
Since, apparently, we extend the `RecheckOptionsBuilder` by `RecheckWebOptionsBuilder` we need to make sure, that it can handle such. With the current implementation (as of v1.5.0) the usage of the builder...
Each time `RecheckImpl#cap()` is being invoked, we trigger `CloudPersistence#save(...)` and upload the aggregated `tests.report` to rehub. Suppose there are 10 tests classes, each consisting of 3 test methods. If `cap()`...
We currently have implementation-specific filters (e.g. for recheck-web) in recheck (under `src/main/resources/filter/`), which is not optimal. Implementations should provide their own filters, so that recheck isn't bloated with filter files...
When we try to assign a step name to a GM or vice versa, three situations can occur: 1. We cannot find a GM for the given step name, so...
Quite often, there are more unique differences than "normal" differences. These normal differences are counted via `ActionReplayResult#getElementDifferences()`, whereas the unique differences are counted via `ActionReplayResult#getUniqueDifferences()`. As can been seen, `getElementDifferences()`...
Taken from `AttributesDifferenceFinder`: ```java private AttributeDifference differenceFor( final IdentifyingAttributes identAttributes, final Serializable expected, final Serializable actual, final String key ) { if ( expected == null ) { return null;...