PHP: Mockery Mock variable $user = Auth::user()





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















So, I am trying to mock a service method.



In my service file:



/**
* Return all Api Keys for current user.
*
* @return Collection
*/
public function getApiKeys(): Collection
{
$user = Auth::user();

return ApiKey::where('org_id', $user->organizationId)->get();
}


How do I mock this?



<?php


namespace AppServices;

use PHPUnitFrameworkTestCase;
use Mockery as m;

class ApiKeysServiceTest extends TestCase
{
public function setUp()
{
parent::setUp();

/* Mock Dependencies */
}

public function tearDown()
{
m::close();
}

public function testGetApiKeys()
{
/* How to test? $user = Auth::user() */
$apiKeysService->getApiKeys();
}


}



In my TestCase class I have:



public function loginWithFakeUser()
{
$user = new GenericUser([
'id' => 1,
'organizationId' => '1234'
]);

$this->be($user);
}


What I want to do is test this method. Maybe this involves restructuring my code so that $user = Auth::user() is not called in the method. If this is the case, any thoughts as to where it should go?



Thanks for your feedback.










share|improve this question

























  • Use a factory to create a user, and then use $this->actingAs($user); See laravel.com/docs/5.6/http-tests#session-and-authentication

    – miken32
    Nov 16 '18 at 22:57


















0















So, I am trying to mock a service method.



In my service file:



/**
* Return all Api Keys for current user.
*
* @return Collection
*/
public function getApiKeys(): Collection
{
$user = Auth::user();

return ApiKey::where('org_id', $user->organizationId)->get();
}


How do I mock this?



<?php


namespace AppServices;

use PHPUnitFrameworkTestCase;
use Mockery as m;

class ApiKeysServiceTest extends TestCase
{
public function setUp()
{
parent::setUp();

/* Mock Dependencies */
}

public function tearDown()
{
m::close();
}

public function testGetApiKeys()
{
/* How to test? $user = Auth::user() */
$apiKeysService->getApiKeys();
}


}



In my TestCase class I have:



public function loginWithFakeUser()
{
$user = new GenericUser([
'id' => 1,
'organizationId' => '1234'
]);

$this->be($user);
}


What I want to do is test this method. Maybe this involves restructuring my code so that $user = Auth::user() is not called in the method. If this is the case, any thoughts as to where it should go?



Thanks for your feedback.










share|improve this question

























  • Use a factory to create a user, and then use $this->actingAs($user); See laravel.com/docs/5.6/http-tests#session-and-authentication

    – miken32
    Nov 16 '18 at 22:57














0












0








0








So, I am trying to mock a service method.



In my service file:



/**
* Return all Api Keys for current user.
*
* @return Collection
*/
public function getApiKeys(): Collection
{
$user = Auth::user();

return ApiKey::where('org_id', $user->organizationId)->get();
}


How do I mock this?



<?php


namespace AppServices;

use PHPUnitFrameworkTestCase;
use Mockery as m;

class ApiKeysServiceTest extends TestCase
{
public function setUp()
{
parent::setUp();

/* Mock Dependencies */
}

public function tearDown()
{
m::close();
}

public function testGetApiKeys()
{
/* How to test? $user = Auth::user() */
$apiKeysService->getApiKeys();
}


}



In my TestCase class I have:



public function loginWithFakeUser()
{
$user = new GenericUser([
'id' => 1,
'organizationId' => '1234'
]);

$this->be($user);
}


What I want to do is test this method. Maybe this involves restructuring my code so that $user = Auth::user() is not called in the method. If this is the case, any thoughts as to where it should go?



Thanks for your feedback.










share|improve this question
















So, I am trying to mock a service method.



In my service file:



/**
* Return all Api Keys for current user.
*
* @return Collection
*/
public function getApiKeys(): Collection
{
$user = Auth::user();

return ApiKey::where('org_id', $user->organizationId)->get();
}


How do I mock this?



<?php


namespace AppServices;

use PHPUnitFrameworkTestCase;
use Mockery as m;

class ApiKeysServiceTest extends TestCase
{
public function setUp()
{
parent::setUp();

/* Mock Dependencies */
}

public function tearDown()
{
m::close();
}

public function testGetApiKeys()
{
/* How to test? $user = Auth::user() */
$apiKeysService->getApiKeys();
}


}



In my TestCase class I have:



public function loginWithFakeUser()
{
$user = new GenericUser([
'id' => 1,
'organizationId' => '1234'
]);

$this->be($user);
}


What I want to do is test this method. Maybe this involves restructuring my code so that $user = Auth::user() is not called in the method. If this is the case, any thoughts as to where it should go?



Thanks for your feedback.







php laravel mockery






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 16 '18 at 20:56







Daltron

















asked Nov 16 '18 at 20:48









DaltronDaltron

311215




311215













  • Use a factory to create a user, and then use $this->actingAs($user); See laravel.com/docs/5.6/http-tests#session-and-authentication

    – miken32
    Nov 16 '18 at 22:57



















  • Use a factory to create a user, and then use $this->actingAs($user); See laravel.com/docs/5.6/http-tests#session-and-authentication

    – miken32
    Nov 16 '18 at 22:57

















Use a factory to create a user, and then use $this->actingAs($user); See laravel.com/docs/5.6/http-tests#session-and-authentication

– miken32
Nov 16 '18 at 22:57





Use a factory to create a user, and then use $this->actingAs($user); See laravel.com/docs/5.6/http-tests#session-and-authentication

– miken32
Nov 16 '18 at 22:57












1 Answer
1






active

oldest

votes


















0














In your testGetApiKeys method you're not setting up the world. Make a mock user (using a factory as suggested in the comments factory('AppUser')->create()), then setup an apiKey again using the factory, then call the method and assert it's what you've setup. An example with your code



public function loginWithFakeUser()
{
$user = factory('AppUser')->create();

$this->be($user);
}

public function testApiSomething()
{
$this->loginWithFakeUser();

// do something to invoke the api...
// assert results
}


A good blueprint for the test structure is:




  • Given we have something (setup all the needed components)

  • If the user does some action (visits a page or whatever)

  • Then ensure the result of the action is what you expect (for example the status is 200)






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53345173%2fphp-mockery-mock-variable-user-authuser%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    In your testGetApiKeys method you're not setting up the world. Make a mock user (using a factory as suggested in the comments factory('AppUser')->create()), then setup an apiKey again using the factory, then call the method and assert it's what you've setup. An example with your code



    public function loginWithFakeUser()
    {
    $user = factory('AppUser')->create();

    $this->be($user);
    }

    public function testApiSomething()
    {
    $this->loginWithFakeUser();

    // do something to invoke the api...
    // assert results
    }


    A good blueprint for the test structure is:




    • Given we have something (setup all the needed components)

    • If the user does some action (visits a page or whatever)

    • Then ensure the result of the action is what you expect (for example the status is 200)






    share|improve this answer




























      0














      In your testGetApiKeys method you're not setting up the world. Make a mock user (using a factory as suggested in the comments factory('AppUser')->create()), then setup an apiKey again using the factory, then call the method and assert it's what you've setup. An example with your code



      public function loginWithFakeUser()
      {
      $user = factory('AppUser')->create();

      $this->be($user);
      }

      public function testApiSomething()
      {
      $this->loginWithFakeUser();

      // do something to invoke the api...
      // assert results
      }


      A good blueprint for the test structure is:




      • Given we have something (setup all the needed components)

      • If the user does some action (visits a page or whatever)

      • Then ensure the result of the action is what you expect (for example the status is 200)






      share|improve this answer


























        0












        0








        0







        In your testGetApiKeys method you're not setting up the world. Make a mock user (using a factory as suggested in the comments factory('AppUser')->create()), then setup an apiKey again using the factory, then call the method and assert it's what you've setup. An example with your code



        public function loginWithFakeUser()
        {
        $user = factory('AppUser')->create();

        $this->be($user);
        }

        public function testApiSomething()
        {
        $this->loginWithFakeUser();

        // do something to invoke the api...
        // assert results
        }


        A good blueprint for the test structure is:




        • Given we have something (setup all the needed components)

        • If the user does some action (visits a page or whatever)

        • Then ensure the result of the action is what you expect (for example the status is 200)






        share|improve this answer













        In your testGetApiKeys method you're not setting up the world. Make a mock user (using a factory as suggested in the comments factory('AppUser')->create()), then setup an apiKey again using the factory, then call the method and assert it's what you've setup. An example with your code



        public function loginWithFakeUser()
        {
        $user = factory('AppUser')->create();

        $this->be($user);
        }

        public function testApiSomething()
        {
        $this->loginWithFakeUser();

        // do something to invoke the api...
        // assert results
        }


        A good blueprint for the test structure is:




        • Given we have something (setup all the needed components)

        • If the user does some action (visits a page or whatever)

        • Then ensure the result of the action is what you expect (for example the status is 200)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 27 '18 at 13:13









        BorisuBorisu

        549412




        549412
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53345173%2fphp-mockery-mock-variable-user-authuser%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Xamarin.iOS Cant Deploy on Iphone

            Glorious Revolution

            Dulmage-Mendelsohn matrix decomposition in Python