Issue #416: test should be updated to reuse inlined to input violation messages

[Brijeshthummar02]

Issue #416

I updated AbstractPatchFilterEvaluationTest to support inline violation messages from input files, while keeping backward compatibility with existing expected.txt files.

Before proceeding further, should this issue also include migration of existing test input bundles to inline violation comments and removal of corresponding expected.txt files, or is the framework-level support sufficient for this PR?

[romani]

Before proceeding further, should this issue also include migration of existing test input bundles to inline violation comments and removal of corresponding expected.txt files,

this is a goal.

[romani]

we can upgrade tests step by step to avoid huge PRs

[Brijeshthummar02]

Before proceeding further, should this issue also include migration of existing test input bundles to inline violation comments and removal of corresponding expected.txt files,

this is a goal.

So i made a small focused migration by moving violations from expected.txt into inline comments for two representative bundles:

• FileTabCharacter/SingleNewLine
• MoveCodeToAnotherFileWithMinorChanges

Removed the corresponding expected.txt files and updated the shared test helper to handle column-prefixed messages.

Should further migration of remaining test bundles be continued in this PR or handled in separate follow-up PRs?

[Brijeshthummar02]

we can upgrade tests step by step to avoid huge PRs

For the testing part, i did some migration in this PR so you can check it. Once this get's merged i will migrate all remaining test bundles one by one.