Hello Aaron. I would agree with you and others that Laravel ecosystem is super cool and powerful. Thanks for the informative video. One thing to notice though, the dusk is not built for someone actually stating at the screen while validating stuff etc, but rather take a big hit on the automation part while using the GUI and markup to identify required components of the page to be or not presented at a certain point. Having that said, you would like to have the fastest testing possible so the typeSlowly to me is just for the coders to view the process of their tests being executed at the time of development, but we should not forget to remove any slowdown parts to make sure the tests runs as quickly and lightly as possible. Btw, great video and thanks for the Laravel Ecosystems serie touching the entire "family". I myself will have to watch or revisit some of the members as we code and develop based on the project needs so sometimes staying away for a while requires you to get back on track by RTFM :)
11:30 since I'm coming from the JS ecosystem, I only wish that getting elements on the page had more "accessible" selectors. I personally like how react-testing-library and Playwright promote using more accessible selectors such as labels or placeholder text. That's how real users see fields and I think it's a really good approach to also test that your UI is accessible as well as asserting whatever you want. Of course there are times when you have to reach for data-* attribute selectors (or something else), but most of the time if you see that you have to use a weird selector to target an element, it's actively discouraged and can tell you that your UI isn't accessible and you can act on it and address it. Other than that I guess Dusk's strength is its super tight integration with Laravel. No other tool can match that.
Hey Aaron, this is really cool. Newbie question: at the end when you test the Reverb website, does that mean that I could, for example, build some kind of test application to test WordPress sites, for example, that are completely separate from the Laravel application that houses the Dusk test suite I'm running?
When I joined my last project, there were no tests. By chance, I came across Laravel Dusk at some point and we experimented with it a little and were thrilled. But then we ran into major problems that cost us a lot of time. The Chrome browser on our Windows development computers was automatically updated. As a result, we received an error message when running the tests that the version of the ChromeDriver did not match the version of the locally installed Chrome browser. So we always had to wait until there was a new, matching version. The customer didn't like this at all and stopped the implementation of the tests completely. Unfortunately, we were unable to find a solution to this problem.
Do we have tool or cli command for writing dusk test automatically? playwright and cypress do it well, you just have to do operations on page and it will write code for you automatically.
Hi Aaron, could you please make a video about how you study before creating a video? I notice you use paper and markers, and I find that interesting because I do that too. Knowing more about your system could help me improve on what I'm doing for research or learning something new.
Hey Aaron , love your videos ... quick question how would you automate a registration process without using browser automation. I got asked in a test and i tried mimicking the post request using guzzle but just trying to be sure. Thanks you're amazing
Dusk is a nice setup. Though we have to use two builds on our pipeline, one for dusk and a second for prod. Anyway, I see you use light IDE, do you benefit something over dark?
