Coverage remained the same at 19.324% when pulling f1e726e on pkiraly:7906-delete-an-extra-space-from-delete-user-api-message into 52fee75 on IQSS:develop.

I extended a test to cover the success message content.

I extended a test to cover the success message content.

@pkiraly I don't think this is needed (we already check the status code). The actual message isn't critical, just success of failure. This is actually a great example, had the test already contained this assert, then it would have failed for the removing of a space - having that fail adds no (or at least little) value.

I don't think this is needed (we already check the status code).
@scolapasta Yes, it did not have a real value per se, but the test would be a safeguard in the future, when somebody want to change the content of the message, e.g. change username to email address. A test proves that there is an expectation regarding to the output, and changing the message might involve changes in the client software and documentation.
If you still think testing it is useless, I delete the test changes.

I don't think this is needed (we already check the status code).
@scolapasta Yes, it did not have a real value per se, but the test would be a safeguard in the future, when somebody want to change the content of the message, e.g. change username to email address. A test proves that there is an expectation regarding to the output, and changing the message might involve changes in the client software and documentation.
If you still think testing it is useless, I delete the test changes.

@pkiraly yes, let's remove - alternatively, if you think it's important output, we should return it as part of a more structured json and not as just part of the message itself. (but that could also be out of scope for now)

@scolapasta done

This PR was developed by Göttingen eResearch Alliance, Germany, and funded by SSHOC, "Social Sciences and Humanities Open Cloud". SSHOC has received funding from the European Union’s Horizon 2020 project call H2020-INFRAEOSC-04-2018, grant agreement #823782.