Don’t train newbies to use Selenium, train them to understand the app and how to create a testable app instead
8:00AM In the morning, I was surfing the web, and then I realized that, in the new "de-centralize" land, I am still seeing a lot of new commercial training courses for testing where the content is heavily focused on UI testing with some cool frameworks or libs such as Selenium, Cypress, Puppeteer,... A long time ago, I myself had a very joyful experience with Selenium IDE and then Selenium WebDriver. At that time, I actually thought that Selenium was a one-size-fits-all set of tools and there was no question asked a big Thanos in the test automation community.
Then things change when I have a chance to work with an app built based on Microservices architecture and using the cloud to host their app. I realize that it’s too late for us to wait for deployment before starting our testing activities, and there is a lot of room for us to leave the comfortable "black-box". Larry Smith (creator of Shift-Left testing methodology) feels the same way when he has the opportunity to test a new login mechanism for Tru 64 UNIX OS https://www.drdobbs.com/shift-left-testing/184404768
I am writing this to recommend you all (trainers, coaches, and mentors) to pause a little bit, clarify our understanding about test automation these days and if possible spend some time reading/viewing these 3 articles below
领英推荐
In the 3rd video, even Simon Stewart, the creator of Selenium WebDriver, warns us to not let the tool control us but use it to do what we want in a defined plan.?
I hope this is helpful to you all who are keeping our young talent in Vietnam growing. I also would like to send my thanks to Larry Smith, Toby Clemson, Ham Vocke, and Simon Stewart for their sharing.