[primer] Create a class for easier comparison of pylint results

[Pierre-Sassoulas]

Type of Changes

	Type
✓	🔨 Refactoring

Description

Follow up to #6973

[coveralls]

Pull Request Test Coverage Report for Build 2528939077

• 37 of 37 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.002%) to 95.287%

---

Totals
Change from base Build 2527590849:	0.002%
Covered Lines:	16600
Relevant Lines:	17421

---

💛 - Coveralls

[github-actions]

🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉

This comment was generated for commit a54c77e

[DanielNoord]

Could you rename this to PylintComparator? At some point I want to make an AstroidComparator 😄

If you're up for it perhaps we could even create an abstract class?

[Pierre-Sassoulas]

What do you mean by astroid comparator ? Comparing a json dump of the generated ast ?

[DanielNoord]

No, using the primer on astroid/main to catch crashes there before we merge them. That would require a different Comparator I think.

[Pierre-Sassoulas]

So it's the basic primer for pylint but for astroid ? It does not need a comparator right ? As if a crash exists it's always problem, and there's no crash on main.

[DanielNoord]

Yeah, but I thinking of maybe running the pylint test suite on some version on astroid main or something like that. The overall goal is to remove the need for pylint-tested label and have all PRs get that automatically.

[Pierre-Sassoulas]

Yeah sure I understood that :) It make sense to test astroid more in the astroid CI, because pylint's CI is already crowded so I think it's a really good idea too.