This test passed because the 2 matched the 241 of the read length. But this is
not what we wanted to test. We expect just one sequence to be ambiguous.

This will help testing the effect of some parameter on all the functional tests.

This will be more flexible.

6577fd78 by @magiraud fixed the UNSEG_AMBIGUOUS, hence the test passes

- stanford*: one sequence in S22 is not segmented
- trd-dd2-dd3*: the short Dd2-Dd3 example has a evalue slightly above 1.0, we set -e 10
- chimera:  one failed test is now passing thanks to e-value

This should be corrected.

As the germlines are displayed, we should look for '->' to ensure we are on the right line

Again, this sequence should not be segmented on IGL, but reported as AMBIGUOUS on TRG and not TOO_FEW_J.

This sequence should not be segmented on IGL, but reported as AMBIGUOUS on TRG.