roch1990 / peon Goto Github PK

Hello there!

My name is Ana. I noted that you use the mutation testing tool in the project.
I am a postdoctoral researcher at the University of Seville (Spain), and my colleagues and I are studying how mutation testing tools are used in practice. With this aim in mind, we have analysed over 3,500 public GitHub repositories using mutation testing tools, including yours! This work has recently been published in a journal paper available at https://link.springer.com/content/pdf/10.1007/s10664-022-10177-8.pdf.

To complete this study, we are asking for your help to understand better how mutation testing is used in practice, please! We would be extremely grateful if you could contribute to this study by answering a brief survey of 21 simple questions (no more than 6 minutes). This is the link to the questionnaire https://forms.gle/FvXNrimWAsJYC1zB9.

Drop me an e-mail if you have any questions or comments ([email protected]). Thank you very much in advance!!

Now pipeline looks like:
every file -> Principles -> file goes trough every rule and every rule has it own report

Its not good, because reports mixed between each other.

How it should be:
Tuple of files -> Principles -> tuple of files goes trough every rule (rule by rule)
Every rule is standalone class.
Tuple of files is Principles property.

Every Rule class has its own report method, that create report (of course, its report!).

And report should be like:

Principle bla-bla-bla.
/src/project/file.py:23
/src/project/file2.py:32
More information: link to yegor256

Principle atata.
....

This looks more pretty.

Create report to file if user choose -o cmd flag with output name (relative or absolute).
Default - to stdout.
To report class add method to_file (create file if need and write to it).
To methods of principles class add option by if-else operator for output channel choosing (file/stdout).

If person, who use this linter want only to know what is invalid - he or she can start liner with flag -s, that only show invalid places and thent exit with 0.
If flag not given - exit with 1 (if was found invalid cases).

A lot of mutual tests (around 50) is falling now.
Should repair.

At now there is only one way to create release - manual.
Need to add this step to travis.
Travis should create only minor versions.

So, result looks like:

• after merge changes to master travis start to deploy release
• release would be created at https://github.com/roch1990/peon/releases
• release name should consists of version (wildcard - X.Y where X is major version, Y - minor version)
• travis autoincrement minor version of release
• description of release should consists of commit list (with links), chained with this release (deff between previous and current releases)

at python 3.7 - all is ok
python 3.8:

AttributeError: module '_ast' has no attribute 'Str'

Now report is not ordered.

But report should loks like this (example):

Principle: No mutable types
file1.py:1
file1.py:3
file2.py:12
source:<link to yegor256 article>

Principle: No null
....

Neew to write bash script, that:
for python 3.0..9:
- pull container with python v3.N (n=0..9 ?)
- clone peon to container
- try to test a some python code by peon
- if exception raised - test should fall
- start test with next version

• if one of version-test fall - exit(127) else exit(0)

• MIT License
• Table of contents
• Development guideline