Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test support for 4.1 -> Some issues found #89

Closed
marxjohnson opened this issue Dec 9, 2022 · 3 comments
Closed

Test support for 4.1 -> Some issues found #89

marxjohnson opened this issue Dec 9, 2022 · 3 comments

Comments

@marxjohnson
Copy link
Contributor

I have tested installation, automated tests, and basic indexing/searching on Moodle 4.1. I found the following minor issues:

  • Unit tests need renaming and namespacing to match current conventions.
  • Some tests use assertions which are deprecated in newer versions of PHPUnit.
  • Tests for proxy configuration fail if a proxy is configured for the development environment.
@dmitriim
Copy link
Member

hey! @marxjohnson have you seen something like following error while working on the plugin for 4.1?


1) search_elastic_esrequest_testcase::test_get
Error: Class 'GuzzleHttp\Middleware' not found

/var/www/catalyst-moodle/search/engine/elastic/tests/esrequest_test.php:60
/var/www/catalyst-moodle/lib/phpunit/classes/advanced_testcase.php:80
phpvfscomposer:///var/www/catalyst-moodle/vendor/phpunit/phpunit/phpunit:97

getting this in our CI for 4.1 upstream branch...

@dmitriim
Copy link
Member

By the way the error is gone on the branch from #90

@marxjohnson
Copy link
Contributor Author

Yes, I saw that in a few places during my 4.1 testing. I think it's to do with the namespacing (or lack of) in test classes meaning it's not finding the Guzzle class, so I think my changes fixed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants