DOCSP-35974: Update one usage example

[norareidy]

JIRA - https://jira.mongodb.org/browse/DOCSP-35974
Staging - https://preview-mongodbnorareidy.gatsbyjs.io/laravel/DOCSP-35974/usage-examples/updateOne/

Checklist

• Add tests and ensure they pass
• Add an entry to the CHANGELOG.md file
• Update documentation for new features

[rachel-mack]

One suggestion:

[norareidy]

I get the following error when running this file:
Could not open input file: vendor/bin/phpunit

[jmikola]

That would get installed by running composer update from the repository root to install all dependencies in composer.json (both require and require-dev).

Was the error above based on following instructions in Contributing: Run Tests. It's not clear to me how this file would even be picked up by the normal test suite (files under tests/), so I'll defer to @GromNaN to follow up here.

[norareidy]

I'm following these instructions, but I was running the command in the wrong folder; here's what I get now:

There was 1 PHPUnit test runner warning:

1) No tests found in class "App\Http\Controllers\UpdateOneTest".

No tests executed!

[jmikola]

#2795 should address this.

[jmikola]

@GromNaN: more generally I don't see a clear benefit to putting PHPUnit test files outside of the tests/ directory like this. This differs from the PHPLIB approach, where we run example/docs scripts from ExamplesTest and assert output.

Based on the current PHPUnit configuration, these files won't be picked up by the test suite (nor tools like phpcs and phpstan). It might make more sense to organize these files within the actual test suite and then have docs refer to them there. And in that case, we can use meaningful namespaces.

[GromNaN]

The namespace is of no particular interest. I think we'll come back to it to clean it up.

[GromNaN]

I updated the example test (formatting and assertions).