Improve tests in Spoon

[surli]

I just had a report from @oscarlvp who is working on software testing that we have a lot of methods not properly tested in Spoon.
For a lot of them we have a coverage, but removing the body of the method does not change at all the test results. For other methods, deciding an arbitrary return value (like return true) does not change either the test results.

So we should improve our test basis. The complete list of badly tested methods (and why) is available there: https://github.com/STAMP-project/descartes-experiments/blob/master/spoon/index.md

[zielint0]

@surli

The complete list of badly tested methods (and why) is available there:

404

we have a lot of methods not properly tested in Spoon.

Please elaborate what is proper testing (in case of Spoon).
I would appreciate some examples.
Mercii in advance.

[oscarlvp]

The list of issues has been placed here
For more information about the way these issues were found please take a look at descartes.
A sample of those issues was inspected before by @surli. The result can be seen here. Those that have marks are the ones that would need a closer look.
I hope this helps.

[zielint0]

¡Gracias hermano!

[KishkinJ10]

can i do this in my GSoC coding period please??

[Rohitesh-Kumar-Jain]

Hi @monperrus,

I have run Descartes on Spoon. Here's my report generated after running.

I have reached the first milestone, I would be glad if someone lets me know what I am supposed to do after this?

[monperrus]

Great milestone, congrats! The next step is to pick one pseudo-tested method and to write a test to better specify it (or to add an assertion in an existing test). Once the test is written, you run descartes again and the method should not be pseudo-tested anymore.

[TheMarvelFan]

Hi is this issue still open?

[MartinWitt]

Yes, feel free to start working on it.