-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI not working #118
CI not working #118
Conversation
Modified `testWorking` URL to the correct one Modified `run` not to have `title: was sent to nil` Added `expressionToReplace` and `newExpression` to most classes representing operators in the mutations
Modified some `expressionToReplace` and `newExpression` that didn't work
Still works as intended, but may be interesting to still try to fix it instead of removing it
Removed all the useless `expressionToReplace` and `newExpression` methods
… method was empty
… method was empty
Added `MTCIMarkdownExporter`, for now it is non usable
Added a simple test to it `Microdown` could be more used to have a better formatting of the content in the file
Using `Microdown` could help us a lot for this issue
First try to manage issues with table format of Markdown
Changed `uninstallMetalinks` to uninstall only if necessary
For |
ok! let's talk quickly about this |
Now the Json exporter is failing
We are getting close! |
Skip test that has a lots of strong dependencies
Nice! Now, Microdown is not available in Pharo 9. |
Changed
nodeToMutate
to adapt to the different operatorsFixed an issue where the data given to the JSON exporter would be a Character instead of a String, breaking the exporter
Added
expressionToReplace
andnewExpression
to operators that needed itChanged URL to the correct one in
JsonExporterTest
The last fix where I commented lines that broke the program seems wrong, I think it would be more cautious if we replaced those lines by something that does the same job instead of just removing it
An example of a CI can be found here, it is very similar to the one already available on the repo
Added the possibility of adding a job summary in the Action that gives the basic information such as the number of tests killed, alive or terminated and the mutation score as well as the commit or the pull request ID