i must press enter on running tests using phpunit in laravel












0














i must press enter on running tests using phpunit in Laravel 5.7.



On every test i get following Message:




1) TestsFeatureDepartmentsTest::a_admin_can_create_a_department
MockeryExceptionBadMethodCallException: Received
Mockery_1_Illuminate_Console_OutputStyle::askQuestion(), but no
expectations were specified




by setting following to false, the error disappear:



public $mockConsoleOutput = false;


After that the window hangs on running the test suite and i need to press enter to run the tests.



How can i fix that?



I´am using Windows 10 + PHPUnit 7.5.1 and Laravel 5.7.19



Thanks in advance!



/** @test */
public function a_admin_can_create_a_department()
{

// $this->withoutExceptionHandling();

$attributes = [
'description' => 'Service',
'accessible_by_depart' => true
];

$this->post('/tools/api/storeDepartment', $attributes);

$this->assertDatabaseHas('departments', $attributes);
}









share|improve this question
























  • Can you post the TestsFeatureDepartmentsTest::a_admin_can_create_a_department code?
    – Peter
    Dec 20 '18 at 23:30










  • @Peter edited the post, see above
    – Daniel Julius
    Dec 21 '18 at 12:13












  • Can you show your $this->post() method too? Basically we need to see where you are setting up your mock.
    – Peter
    Dec 21 '18 at 21:32
















0














i must press enter on running tests using phpunit in Laravel 5.7.



On every test i get following Message:




1) TestsFeatureDepartmentsTest::a_admin_can_create_a_department
MockeryExceptionBadMethodCallException: Received
Mockery_1_Illuminate_Console_OutputStyle::askQuestion(), but no
expectations were specified




by setting following to false, the error disappear:



public $mockConsoleOutput = false;


After that the window hangs on running the test suite and i need to press enter to run the tests.



How can i fix that?



I´am using Windows 10 + PHPUnit 7.5.1 and Laravel 5.7.19



Thanks in advance!



/** @test */
public function a_admin_can_create_a_department()
{

// $this->withoutExceptionHandling();

$attributes = [
'description' => 'Service',
'accessible_by_depart' => true
];

$this->post('/tools/api/storeDepartment', $attributes);

$this->assertDatabaseHas('departments', $attributes);
}









share|improve this question
























  • Can you post the TestsFeatureDepartmentsTest::a_admin_can_create_a_department code?
    – Peter
    Dec 20 '18 at 23:30










  • @Peter edited the post, see above
    – Daniel Julius
    Dec 21 '18 at 12:13












  • Can you show your $this->post() method too? Basically we need to see where you are setting up your mock.
    – Peter
    Dec 21 '18 at 21:32














0












0








0







i must press enter on running tests using phpunit in Laravel 5.7.



On every test i get following Message:




1) TestsFeatureDepartmentsTest::a_admin_can_create_a_department
MockeryExceptionBadMethodCallException: Received
Mockery_1_Illuminate_Console_OutputStyle::askQuestion(), but no
expectations were specified




by setting following to false, the error disappear:



public $mockConsoleOutput = false;


After that the window hangs on running the test suite and i need to press enter to run the tests.



How can i fix that?



I´am using Windows 10 + PHPUnit 7.5.1 and Laravel 5.7.19



Thanks in advance!



/** @test */
public function a_admin_can_create_a_department()
{

// $this->withoutExceptionHandling();

$attributes = [
'description' => 'Service',
'accessible_by_depart' => true
];

$this->post('/tools/api/storeDepartment', $attributes);

$this->assertDatabaseHas('departments', $attributes);
}









share|improve this question















i must press enter on running tests using phpunit in Laravel 5.7.



On every test i get following Message:




1) TestsFeatureDepartmentsTest::a_admin_can_create_a_department
MockeryExceptionBadMethodCallException: Received
Mockery_1_Illuminate_Console_OutputStyle::askQuestion(), but no
expectations were specified




by setting following to false, the error disappear:



public $mockConsoleOutput = false;


After that the window hangs on running the test suite and i need to press enter to run the tests.



How can i fix that?



I´am using Windows 10 + PHPUnit 7.5.1 and Laravel 5.7.19



Thanks in advance!



/** @test */
public function a_admin_can_create_a_department()
{

// $this->withoutExceptionHandling();

$attributes = [
'description' => 'Service',
'accessible_by_depart' => true
];

$this->post('/tools/api/storeDepartment', $attributes);

$this->assertDatabaseHas('departments', $attributes);
}






laravel windows-10 phpunit mockery






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 21 '18 at 12:15

























asked Dec 20 '18 at 20:11









Daniel Julius

65




65












  • Can you post the TestsFeatureDepartmentsTest::a_admin_can_create_a_department code?
    – Peter
    Dec 20 '18 at 23:30










  • @Peter edited the post, see above
    – Daniel Julius
    Dec 21 '18 at 12:13












  • Can you show your $this->post() method too? Basically we need to see where you are setting up your mock.
    – Peter
    Dec 21 '18 at 21:32


















  • Can you post the TestsFeatureDepartmentsTest::a_admin_can_create_a_department code?
    – Peter
    Dec 20 '18 at 23:30










  • @Peter edited the post, see above
    – Daniel Julius
    Dec 21 '18 at 12:13












  • Can you show your $this->post() method too? Basically we need to see where you are setting up your mock.
    – Peter
    Dec 21 '18 at 21:32
















Can you post the TestsFeatureDepartmentsTest::a_admin_can_create_a_department code?
– Peter
Dec 20 '18 at 23:30




Can you post the TestsFeatureDepartmentsTest::a_admin_can_create_a_department code?
– Peter
Dec 20 '18 at 23:30












@Peter edited the post, see above
– Daniel Julius
Dec 21 '18 at 12:13






@Peter edited the post, see above
– Daniel Julius
Dec 21 '18 at 12:13














Can you show your $this->post() method too? Basically we need to see where you are setting up your mock.
– Peter
Dec 21 '18 at 21:32




Can you show your $this->post() method too? Basically we need to see where you are setting up your mock.
– Peter
Dec 21 '18 at 21:32












1 Answer
1






active

oldest

votes


















0














So now I finally found the solution.



On my migration from Laravel 5.1 to Laravel 5.2 (a long time ago) i forgot to add the following lines to the config/app.php File:



    /*
|--------------------------------------------------------------------------
| Application Environment
|--------------------------------------------------------------------------
|
| This value determines the "environment" your application is currently
| running in. This may determine how you prefer to configure various
| services the application utilizes. Set this in your ".env" file.
|
*/
'env' => env('APP_ENV', 'production'),


Now everything works fine.



Greetings Daniel






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%2f53875387%2fi-must-press-enter-on-running-tests-using-phpunit-in-laravel%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














    So now I finally found the solution.



    On my migration from Laravel 5.1 to Laravel 5.2 (a long time ago) i forgot to add the following lines to the config/app.php File:



        /*
    |--------------------------------------------------------------------------
    | Application Environment
    |--------------------------------------------------------------------------
    |
    | This value determines the "environment" your application is currently
    | running in. This may determine how you prefer to configure various
    | services the application utilizes. Set this in your ".env" file.
    |
    */
    'env' => env('APP_ENV', 'production'),


    Now everything works fine.



    Greetings Daniel






    share|improve this answer




























      0














      So now I finally found the solution.



      On my migration from Laravel 5.1 to Laravel 5.2 (a long time ago) i forgot to add the following lines to the config/app.php File:



          /*
      |--------------------------------------------------------------------------
      | Application Environment
      |--------------------------------------------------------------------------
      |
      | This value determines the "environment" your application is currently
      | running in. This may determine how you prefer to configure various
      | services the application utilizes. Set this in your ".env" file.
      |
      */
      'env' => env('APP_ENV', 'production'),


      Now everything works fine.



      Greetings Daniel






      share|improve this answer


























        0












        0








        0






        So now I finally found the solution.



        On my migration from Laravel 5.1 to Laravel 5.2 (a long time ago) i forgot to add the following lines to the config/app.php File:



            /*
        |--------------------------------------------------------------------------
        | Application Environment
        |--------------------------------------------------------------------------
        |
        | This value determines the "environment" your application is currently
        | running in. This may determine how you prefer to configure various
        | services the application utilizes. Set this in your ".env" file.
        |
        */
        'env' => env('APP_ENV', 'production'),


        Now everything works fine.



        Greetings Daniel






        share|improve this answer














        So now I finally found the solution.



        On my migration from Laravel 5.1 to Laravel 5.2 (a long time ago) i forgot to add the following lines to the config/app.php File:



            /*
        |--------------------------------------------------------------------------
        | Application Environment
        |--------------------------------------------------------------------------
        |
        | This value determines the "environment" your application is currently
        | running in. This may determine how you prefer to configure various
        | services the application utilizes. Set this in your ".env" file.
        |
        */
        'env' => env('APP_ENV', 'production'),


        Now everything works fine.



        Greetings Daniel







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 27 '18 at 21:35

























        answered Dec 27 '18 at 7:19









        Daniel Julius

        65




        65






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f53875387%2fi-must-press-enter-on-running-tests-using-phpunit-in-laravel%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

            Mossoró

            Error while reading .h5 file using the rhdf5 package in R

            Pushsharp Apns notification error: 'InvalidToken'