Found 4 warning messages in watchdog that showed up after loading the page admin/config/development/testing:
Strict warning: Declaration of WebformSubmissionTestCase::setUp() should be compatible with WebformTestCase::setUp($added_modules = Array) in _registry_check_code() (line 176 of sites\all\modules\contrib\webform\tests\submission.test).
Strict warning: Declaration of WebformPermissionsTestCase::setUp() should be compatible with WebformTestCase::setUp($added_modules = Array) in _registry_check_code() (line 67 of sites\all\modules\contrib\webform\tests\permissions.test).
Strict warning: Declaration of WebformConditionalsTestCase::setUp() should be compatible with WebformTestCase::setUp($added_modules = Array) in _registry_check_code() (line 182 of sites\all\modules\contrib\webform\tests\conditionals.test).
Strict warning: Declaration of WebformComponentsTestCase::setUp() should be compatible with WebformTestCase::setUp($added_modules = Array) in require_once() (line 10 of sites\all\modules\contrib\webform\tests\components.test).
Comments
Comment #1
hass commentedAehm, what is this code supposed to do?
Are you aware how to load optional modules for QA testing? You can add
test_dependenciesto your info file. This will download token module when a test is running on d.o, but your module will not depend ontoken! Hope this helps... :-)Comment #2
danchadwick commentedA patch would be awesome. ;)
Comment #3
danchadwick commented@hass -- can you post a patch? Your help would be appreciated!!
Comment #4
danchadwick commentedThe declaration of setup has been updated. Since we can't get dependencies, much less test_dependencies to work in the .info file, I'm marking this as closed, with a reference to the issue we are having with the testbot.
If someone with expertise here could help with a patch in #2244979: Figure out why testbot is failing all patches, that sure would be awesome.
Comment #5
hass commentedI think the other case is a duplicate of this patch here. At least #1 has the code for a propper patch that the other case has for sure NOT.
If I get an answer to my questions in #1 - I can share a patch.
Comment #6
danchadwick commented#1 has already been committed. There are no more strict warnings.
There are two questions in #1.
I didn't write it, but I infer that it intends to enable webform and, if available on the testbot, token.
No.
Please feel free to post a patch or help out in #2244979: Figure out why testbot is failing all patches.
Comment #7
hass commented#1 has been committed? Where? I noted that the code in #1 is WRONG. And added the 1 liner fix there. This has not committed and the broken code also need to be fixed.
Do not close cases you do not understand, please.
Comment #8
hass commentedPlease note that
test_dependencyrequires at least 6 or 12 hours to be committed before d.o testbot use this setting. At least in the past...This is not testable with the testbot and requires a "blind" commit.
Comment #11
danchadwick commentedThank you for the patch. It removes the ability to test when token is missing from the environment, which I believe to be intentional. I committed the test_dependency to .info.
Comment #12
hass commentedCommit the rest, too. This is a bug.
Comment #13
danchadwick commentedThe tests behave differently depending upon whether token is available at the time of the test. In the commit in which this was added (a66f61f), there is a test for token within the test itself. Therefore, I presume the intention on quicksketch is to allow the test to run with or without token, such that the optional support for token can be tested.
Thank you for your efforts in this issue. Assuming that tests continue to run once the d.o infrastructure catches up with what I committed in #10, this issue is closed. I will not remove the flexibility to test with and without token.
Comment #14
hass commentedI'm sure that code was added as he was not aware of test_dependency. token is optional and was therefore not downloaded by the test bot.
Now token is always available as test_dependency has been added and the condition is no longer necessary. This was by 99% a workaround to get the tests passing. As this is no longer required this useless code can be removed and should be removed.
Comment #15
danchadwick commentedNo, token is not always available by test_dependency. My reading of the commit that added support for test_dependency is that such modules become recommended, not required for simpletest. Therefore if token is not present in the test environment, the tests will continue to run, allowing tests to test the functionality of webform both with and without token installed.
Feel free to contact quicksketch offline. As maintainer, I am closing this issue. If quicksketch feels that the issue should be handled differently, he can do so. You are not the maintainer. Do not reopen.
Comment #16
hass commentedWhat? You do not understand how this works.
If test_dependency is set, the testbot will ALWAYS download token. Therefore the situation that the tests are running and token is not available does not exists any longer.
Comment #17
danchadwick commentedFirst, my apologies. I see that the derived webform boilerplate setup methods still had the old signature, throwing strict warnings. Committed to 7.x-4.x and 8.x.
You have not thought about local testing environments.

Comment #18
hass commentedIf you do not have token installed the tests must fail. Otherwise testing is useless to run tests. If you test a module you must test all features and not only a few.
Please commit my changes. Why is this bullsh** sooo a challenge here?
Comment #19
danchadwick commented<summoning all my patience and courtesy>
Because you can write tests for when token is not available, since it is an optional module. And currently webform has such a contingency. Your change would prohibit this, reducing the possible test coverage for webform.
I have a valid reason, which I have tried to explain without success, and which I have demonstrated above. This is my decision to make. I appreciate your help in the issue queue. This issue is closed. Your trivial change, which makes zero difference to the testbot environment, but which removes additional testing options for local environments, will simply not be committed. Please accept this and move on to meaningful work.
I'm sure you use your discretion when dealing with issues in the modules you maintain. Please afford me the same courtesy.
</patience and courtesy>
Comment #22
hass commentedIf you'd like to run a test once with and once without token you need two tests. Otherwise this cannot handled by the testbot. Local development is not what we write tests for. Testing is an automated process. It can run locally, but the intention is mostly for automated testing. Nothing else. Show me only one place in core that works this way, please.
Comment #23
hass commentedLike it or not. This patch changes document that the cruft should be removed once
test_dependenciesfeature is available. This code may have been written before I asked fortest_dependenciesand testbot maintainers implemented this ~2 years ago.Comment #25
hass commentedComment #27
danchadwick commented