Base Test Class full of Goodies

Hi, I have same error depreciation with Symfony 5.3 and I do the same thing as you did. I created file services_test.yaml in config and put any thing you write. But when I run the test, it says:

Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: You have requested a non-existent service "test.security.password_hasher".
Its seems the services_test.yaml not works.
Did I miss the step to tell phpunit use that config in services_test.yaml? Any other suggests to do the encode password stuff in test?
Many thanks

HeyDang

That's odd. By default, PHPUnit should run in the test environment so your Kernel will load both config files services.yaml & services_test.yaml. Double check that the file lives inside config/ and the name is correct. You could also try deleting the cache manually rm -r var/cache

Cheers!

deleting the cache this way (instead of c:c) was key to solve the mistery here. thanks MolloKhan

Just in case anyone is wondering: you need to use --env=test for cache:clear to have an effect on your test cases. With this, the solution worked fine on my machine ;)
services_test.yaml

services:
  test.security.password_hasher:
    alias: 'Symfony\Component\PasswordHasher\Hasher\UserPasswordHasherInterface'
    public: true

Hey Jonas,

You're totally right! By default, the cache:clear command will clear the cache for the dev env, but if you want to clear it for a different env - you should specify it explicitly with --env=.... Thanks for pointing it out and confirming it works for you!

Cheers!

Hey André,

I think in this situation it's fine what you did, and since you defined the service only for the test environment I don't see any potential problem to your approach.

Cheers!

Hey, Diego.

Nice! Thank you for the quick reply.
Keep up the great work and support!

Cheers!

Hi André,

Try something like this

`

use Symfony\Component\PasswordHasher\Hasher\PasswordHasherFactory;

class SomeClasse extends ApiTestCase

public function someFunction()
{
$factory = new PasswordHasherFactory(['auto' => ['algorithm' => 'bcrypt'], 'memory-hard' => ['algorithm' => 'sodium'],]);
$passwordHasher = $factory->getPasswordHasher('auto');
$hashedPassword = $passwordHasher->hash($plainPasssord);

$user = new User();
$user->setEmail($email);
$user->setUsername(substr($email, 0, strpos($email, '@')));
$user->setPassword($hashedPassword);
}

}
`

I solved it so.

--
Regards,
Alexander Sumkin

Thanks!! it worked for me in symfony 5.4

Hey @Alexander

Thanks for your work around, that's also valid but personally, I prefer the other option because you don't have to worry about instatiation the PasswordHasher service. Making services public for the test environment it's not a bad thing actually

Cheers!

Hey Cerpo,

Difficult to say, coudl you double check the namespace you've used in that class? Is it the same namespace we used in the screencast? Btw, did. you download the course code and start from the start/ directory? Or did you follow this course on your own project / newer Symfony version? Also, could you share the exact error message you see? It would help us to give you some hints on it :)

Cheers!

Hi Victor. Many thanks for the anwser.
Watching the next chapter, i had an intuition. I moved the self::createClient at 1st line of the function ... and guess what : Pb solved. I can now keep the ReloadTrait up and the test pass as it should.

Before moving the self::createClient on 1st line of the function, it was acting like the create user persist did not work (login failed, invalid credentials) . But I knew the persist was working, because when i commented the trait , all was fine ( user created, login passed ) .

I now think that the CreatClient triggered the Reload trait after the createUser. ( thus , why it's advise in the next chapter to put it on 1st line to let magic happen :) ) .

Hey Cerpo,

Great, happy to hear you were able to solve this problem, good thinking about watching the next chapter :)

Cheers!

Hey Roland W.!

Hmm. That indeed looks weird. It "feels" to me as if PHP is starting a real session... but it should be using a "mock" session in the test environment. I would check into that. Specifically, you should have some config - probably in config/packages/test/framework.yaml that looks like this: https://github.com/symfony/recipes/blob/master/symfony/framework-bundle/4.4/config/packages/test/framework.yaml - I would check there first. But, I'm doing some guessing. You have, unfortunately, a pretty old Symfony version. So we can't rule out that there is some weird behavior due to that :/.

Cheers!

Hey Ben G.!

Let's see what we can figure out :).

>1) Why is that ?

I'm not completely sure. As long as your CustomApiTestCase lives in a src/Test/CustomApiTestCase.php file and that file has the correct class name (CustomApiTestCase) and namespace (App\Test), Composer's autoloader should find it. These class not found things are usually something minor like that. The other possibility is that PHPUnit isn't loading your autoloader - that's normally handled thanks to your phpunit.xml.dist file - it has a bootstrap config that points to a file that initializes the autoloader - for example - https://github.com/symfony/recipes/blob/e6fdf8eff6dd5f5a19bc7aedfac491c60f2121cc/symfony/phpunit-bridge/5.1/phpunit.xml.dist#L8

2) Why do we move our CustomApiTestCase in src/Test ? That's make two tests folder, which can be confusing.
-> My test works if CustomApiTestCase is in Tests folder

That's a good question. This is a matter of "taste" My perspective is that CustomApiTestCase is not itself a "test" - it's a helper class. So I put it in the src/ directory. But that doesn't mean I'm correct. You could argue that even though this isn't itself a test class, it exists for our tests, not our normal code, and so should live in tests/.

And, you ARE free to put things in either src/ or test/. A Symfony project, by default, it set up to autoload from both folders. The default "new project" composer.json skeleton - https://github.com/symfony/skeleton/blob/5.x/composer.json - has this:

    "autoload": {
        "psr-4": {
            "App\\": "src/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "App\\Tests\\": "tests/"
        }
    },

This means that you can put things into the tests/ directory, as long as the namespace starts with App\Tests.

So hopefully that explains how classes are loaded in both directories and the fact that you should totally feel ok putting tour CustomApiTestCase inside tests/ ;).

Cheers!

Thanks for your reactivity and you well explained anwser !

1) Ok, that's what I thought. When you start a new language/framework, is usually useful to ask dumb questions. I'll discuss what my team prefers.

2) Last time I did, I had no errors in PHPStorm. So I try again, and this time it works. I may have write my test folder in lowercase. Anyway, now it works and I totally got it, thanks again !

In my case the problem was that I created folder name in lowercase
"test" and had same error. after renaming to Test this works fine!

The test directory name has to match to what you have in the autoload-dev.psr-4 key and in your phpunit.xml file

Cheers!

Hey Vishal T.!

Let's see if we can figure this out :).

First, are you using API Platform 2.5? If so, then you don't need to copy any of our test code from this chapter - https://symfonycasts.com/sc... - because API Platform 2.5 has all of these classes. I believe you *are* using API Platform 2.5, which is why you're having the issue. So, you can make your life simpler by not copying any of those files and extending the ApiTestCase directly from ApiPlatform :).

But, to your specific error, I think you did copy the test files, but I think you might be missing this services_test.yaml file - https://symfonycasts.com/sc... (but I could be wrong, that's just a guess). However, either way, if you're on API Platform 2.5, the best solution is to just use *their* test code and delete your src/ApiPlatform/Test/ directory entirely).

Cheers!

Hey Sebastian,

Yes, I think I'd agree with you. Well, it depends... first of all, it's not a course about testing, so we didn't want to focus on testing strategy too much, mostly just the general idea of it, and for simplicity doing those things in one method was great as you can see, a little code, and users who does not care about testing (though we hope we don't have such users here :p ) may easily skip that part. Also, in defense of the current implementation I'd say that you can also easily add custom errors messages to PHPUnit's assert methods that would also give you a lot of context about what exactly test failed. But you're right, best practice would be to split those tests. And I think we're talking about this in our PHPUnit course here: https://symfonycasts.com/sc... - which has focus on testing.

Thank you for understanding!

Cheers!

Yep, I'd agree too :). I admit, I was taking some shortcuts on this one. A best practice would be to do exactly what you said. I will *also* admit that I'm not perfect on this - it's tempting to "re-use" your already-setup-and-ready-test to assert more things". But yea, ultimately, you "pay the price" later on when it's harder to debug :).

Cheers!

Hey Amjed N.

Good questions. I suppose holding CustomApiTestCase inside src/ is just to separate some reusable code from tests, and to keep tests/ directory clean only for executable tests.

And about your note sometimes it's better to not reuse existing $client object, and instantiate new one for each test. Because client can save some info about previous request and this can cause unexpected behavior.

Cheers :)

Hi sadikoff

I understand your point about having a clean tests/ directory but the thing is, my production build is loading my CustomApiTestCase and trying to load Alice's ReloadDatabaseTrait as well.

Of course, alice is dev dependency so it doesn't work.

I'm fairly new to php and autoloaders, do you have any tips to avoid loading the Test directory outside of testing env?
I could probably do as amjed said and move the Test directory in tests/ but then I can't get my imports to work.

I tried having a tests/Test directory with the namespace App\Test, then App\Test\Test. Nothing :(

Looking forward to your answer !

Hey Philippe B.

Try to exclude Test/ directory from autowiring. By default symfony excludes Tests/ directory you can find it inside config/services.yaml file look at App\: definition. Just add your Test directory or rename your directory to correspond default configuration.

Cheers!

Hi sadikoff

Perfect, it works like a charm!
Thank you so much for your quick reply

Cheers!

Hey Vladimir,

Thank you for your respond.

Okay for the first point.

For the second one, you're right we must instanciate for each test a client. So I put the instansation of the $client in the setUp() method into the CustomApiTestCase.

Cheers :)