{"id":28,"date":"2020-01-15T11:23:27","date_gmt":"2020-01-15T11:23:27","guid":{"rendered":"https:\/\/cebucodesolutions.com\/blog\/?p=28"},"modified":"2020-01-15T11:23:27","modified_gmt":"2020-01-15T11:23:27","slug":"disabling-html5-form-validation-for-laravel-dusk-tests","status":"publish","type":"post","link":"https:\/\/cebucodesolutions.com\/blog\/2020\/01\/15\/disabling-html5-form-validation-for-laravel-dusk-tests\/","title":{"rendered":"Disabling HTML5 form validation for Laravel Dusk tests"},"content":{"rendered":"\n
If you\u2019re testing form validation using Laravel Dusk, you\u2019ve probably\n hit a scenario where the form submission is blocked by Chrome before \nit\u2019s sent to the server because of HTML5 form validation.<\/p>\n\n\n\n
HTML5 form validation blocks a submission when you add an attribute such as required<\/code> to an input element, or you use type=\"email\"<\/code>. In your Laravel Dusk tests, you\u2019ll probably see this manifesting as a client-side popup dialog in your failing test screenshots.<\/p>\n\n\n\n<\/figure>\n\n\n\n
This is a really tricky thing to test. Since it happens completely \nclient-side without modifying the DOM, it\u2019s hard to assert that the \nerror appears. Even if you do work out a hacky way to do it, it\u2019s not \nactually testing that your web application\u2019s form validation is working.\n You\u2019re essentially just testing that Chrome supports HTML5 form \nvalidation, and I\u2019m sure the Google\/Chromium teams have their own tests \nfor that. \ud83d\ude42<\/p>\n\n\n\n
Your first thought may be to try to disable HTML5 form validation using ChromeOptions<\/code> in DuskTestCase<\/code>. Unfortunately there is no such option. That really only leaves one way: adding the novalidate<\/code>\n property to your HTML forms. This attribute, when applied to a HTML \nform, disables the browser\u2019s native form validation. But this has its \nown drawback in that it disables a perfectly useful feature that \nprobably provides value to your users.<\/p>\n\n\n\n
Thankfully, Dusk allows you to inject JavaScript onto the page at runtime!<\/strong> Using this feature, we can dynamically inject a small code snippet that iterates over the forms on the page and adds the novalidate<\/code> attribute automatically, just for your tests<\/strong>. By adding this browser macro to DuskTestCase<\/code>:<\/p>\n\n\n\n
Thankfully, Dusk allows you to inject JavaScript onto the page at runtime!<\/strong> Using this feature, we can dynamically inject a small code snippet that iterates over the forms on the page and adds the novalidate<\/code> attribute automatically, just for your tests<\/strong>. By adding this browser macro to DuskTestCase<\/code>:<\/p>\n\n\n\n
public static function prepare()\n{\n static::startChromeDriver();\n\n Browser::macro('disableClientSideValidation', function () {\n $this->script('for(var f=document.forms,i=f.length;i--;)f[i].setAttribute(\"novalidate\",i)');\n\n return $this;\n });\n}<\/code><\/pre>\n\n\n\n
\nyou can then call it within your tests like so:\n\n<\/p>\n\n\n\n
$this->browse(function (Browser $browser) {\n $browser->visit('\/register')\n ->disableClientSideValidation()\n ->type('email', 'notvalidemail')\n ->click('@submit')\n\n ->assertPathIs('\/register')\n ->assertSee('The email must be a valid email address.');\n});<\/code><\/pre>\n\n\n\n
\nAnd viola! The result is you\u2019re actually testing your application\u2019s form validation, and you don\u2019t have to give up HTML5 form validation to do it<\/strong>.\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
![\"\"](\"https:\/\/cebucodesolutions.com\/blog\/wp-content\/uploads\/2020\/01\/Screenshot-2020-01-02-at-7.58.23-PM-1024x241.png\")
<\/figure>\n\n\n\n