[
https://issues.apache.org/jira/browse/OAK-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863327#comment-15863327
]
Michael Dürig commented on OAK-5600:
------------------------------------
bq. BTW, how does one get a broken repository in a reproducible way?
This is the tricky bit... I once resorted to storing a zip of a repository as
resource. However this didn't work well as it was nearly impossible to maintain
and evolve. I wouldn't recommend it.
Instead you could try directly manipulating tar files: use the {{RecordId}}
from a given node/property to determine at what position in a tar file it is
stored and corrupt it.
> Test coverage for CheckCommand
> ------------------------------
>
> Key: OAK-5600
> URL: https://issues.apache.org/jira/browse/OAK-5600
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: run, segment-tar
> Reporter: Andrei Dulceanu
> Assignee: Andrei Dulceanu
> Priority: Minor
> Labels: tooling
> Fix For: 1.7.0, 1.8
>
> Attachments: OAK-5600.patch
>
>
> We should add tests for {{o.a.j.o.r.CheckCommand}} in order to validate
> recent changes introduced by adding/removing options and their arguments (see
> OAK-5275, OAK-5276, OAK-5277, OAK-5595). There is also a new feature
> introduced by OAK-5556 (filter paths and refactoring proposed) which must be
> thoroughly tested in order to avoid regressions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
