Refactor AccountControllerTest

[rickybustillos]

Old AccountController.create()
adc7241#diff-b576dad9d2beffbe7963007dfed60c1e5e4fe7125b41dac8310d8ddf28bd7859

Old AccountControllerTest
adc7241#diff-44417e048b8ed9cce7166e64136a1fc8e813fb67c95b6fa97802c1e551bd60d3

Updated AccountController.create()
5089341#diff-b576dad9d2beffbe7963007dfed60c1e5e4fe7125b41dac8310d8ddf28bd7859

    // todo: refactor this test
    @isTest
    public static void givenRequestAccountWhenPostToServerThenCreateAnAccount() {

        Account account = AccountController.create(AccountFixtureFactory.newAccount());

        System.assert(account.Id != null);
    }

[rickybustillos]

In class, the method's return is changed to void. But to carry out the test it is necessary to return the response to validate, for example, the response status code. The question is: Is it a good practice to put a return in @HttpPost method? Or is there another better way to do this?