Make integration tests independent

This creates a dedicated test suite for integration tests. All of them
can be run independently, and there is no order dependency - previously,
all integration tests needed the installer test to run first, and they
would fail if installation failed.

Now, the developer will have to set up a Flarum database to be used by
these tests. A setup script to make this simple will be added in the
next commit.

Small tradeoff: the installer is NOT tested in our test suite anymore,
only implicitly through the setup script. If we decide that this is a
problem, we can still set up separate, dedicated installer tests which
should probably test the web installer.
This commit is contained in:
Franz Liedke
2019-01-30 21:15:27 +01:00
parent 4d10536d35
commit cf746079ed
22 changed files with 416 additions and 419 deletions

View File

@ -18,24 +18,33 @@ class CreateTokenControllerTest extends ApiControllerTestCase
{
protected $controller = CreateTokenController::class;
public function setUp()
{
parent::setUp();
$this->prepareDatabase([
'users' => [
$this->normalUser(),
],
]);
}
/**
* @test
*/
public function user_generates_token()
{
$user = $this->getNormalUser();
$response = $this->call($this->controller, null, [], [
'identification' => $user->username,
'password' => $this->userAttributes['password']
'identification' => 'normal',
'password' => 'too-obscure'
]);
$data = json_decode($response->getBody()->getContents(), true);
$this->assertEquals($user->id, $data['userId']);
$this->assertEquals(2, $data['userId']);
$token = $data['token'];
$this->assertEquals($user->id, AccessToken::findOrFail($token)->user_id);
$this->assertEquals(2, AccessToken::findOrFail($token)->user_id);
}
}