this test did not perform any assertions

@nickywan123 you do not check anything here (no assertions). At least you can do

/**
     *  @test
     * */
    public function unauthenticated_users_may_not_add_reply(){
        //$this->expectException('Illuminate\Auth\AuthenticationException');
        $thread = factory('App\Thread')->create();
        $reply = factory('App\Reply')->create();

        $response = $this->post($thread->path().'/replies', $reply->toArray());
       
        $response->assertRedirect('/login');
    }

You could assert that you are redirect to /login, also, use make() instead of create() to the reply, and assert that database has no records in replies table

$thread = factory('App\Thread')->create();
$reply = factory('App\Reply')->make();

$this->post($thread->path().'/replies', $reply->toArray());

$this->assertDatabaseMissing('replies', $reply->toArray());

@silencebringer so in any test cases in laravel, I need to use assert()?

@sergiu17 Why do you use make() instead of create()?

It is wrong?

@nickywan123 yes, it's wrong, if you use create - it create a new record, and right to the next line you send a post request to create another one..you will end up with two replies in your database.

let's write a test to check if authenticated user can leave a reply with create

$this->actingAs(factory('App\User')->create());

$thread = factory('App\Thread')->create();
$reply = factory('App\Reply')->create(); // we already have a reply in a database

$this->post($thread->path().'/replies', $reply->toArray());

$this->assertDatabaseCount('replies', 1); // this explains why you need to use make

@nickywan123 yes, you must have at least 1 assertion in your test

Great! I learn a lot too..

@nickywan123 Well, the idea of tests is that you actually test something. So you usually set something up, perform an action, and then perform assertions on the results. This is known as act–arrange–assert.