Remove aiida_tests entry point group and parser_tests

[sphuber]

Fixes #1091

The aiida_tests entry point was added as a temporary replacement until
the plugin test fixtures came available. These have been available for a
while now and since no plugins rely on the entry point group we remove
it. Additionally, the test_parsers was a first implementation to test
parser plugins, but this can be done more elegantly with pytest and
the plugin fixtures, therefore it is removed.

[sphuber]

Note, I have gone through all the plugins on the registry and looked at their setup.json and none of them use the aiida.tests entry point group except for aiida-nwchem and aiida-castep. The former we control and we can easily migrate to use pytest with the fixtures. @zhubonan are you still relying on the aiida.tests entry point, which contains one test for the CastepCalculation or have you also migrated to using pytests?

[coveralls]

Coverage decreased (-0.04%) to 71.623% when pulling d0ac414 on sphuber:fix_1091_parsers_tests_entry_point into 5c17bda on aiidateam:develop.

[zhubonan]

I still use it for 0.12.x but it is no longer used in the 1.0.0 branch as all tests has been migrated. I have not updated the setup.json yet probably. Please go ahead and remove the entrypoint. On 17 April 2019 18:21:25 Sebastiaan Huber <notifications@github.com> wrote: Note, I have gone through all the plugins on the registry and looked at their setup.json and none of them use the aiida.tests entry point group except for aiida-nwchem and aiida-castep. The former we control and we can easily migrate to use pytest with the fixtures. @zhubonan<https://github.com/zhubonan> are you still relying on the aiida.tests entry point, which contains one test for the CastepCalculation or have you also migrated to using pytests? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#2778 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AIBAYF7RHYD5QO7SMSOUK2DPQ5MBJANCNFSM4HGWH47A>.