During the recent years I started to feel bad since I quit everything on my country and move to Ireland, my Job as a Quality Engineer Automation using Selenium was one of the most difficult decision I ever take.
that job teached me so many things that now learning about HTML and CSS from Scratch again made me think about my time as a QA and always asking the front developers about his job.
Now I have double knowledge to starting to compare some stuff I remember:
- Since Selenium WebDriver allows test automation in various browsers, designers and developers must ensure that applications are compatible with a variety of popular browsers. This means that interfaces should be designed and developed with differences in performance and rendering in mind for different browsers. (A commong thing to do here was to validate colors on buttons according to the figma design.
- For Selenium to interact with interface elements, unique identifiers must be provided to HTML elements (such as ID, name, classes, etc.). Designers need to collaborate with developers to ensure that these identifiers are available and stable, facilitating test automation with Selenium. This means you have to use standards for naming components on the DOM.
- With the proliferation of devices and screen sizes, Selenium is also used for testing on mobile devices. This implies that designers must ensure that interfaces are responsive and appear and function correctly on a variety of devices and resolutions, making the designing process more accurate and solid.
an extra thing to know is the difference between Selenium Webdriver and Selenium Robot (RC), the first one is a library to make automated Integration tests during the development process and the second one is similar but limited, just giving you the chance to record everything and repeat the process with several limitations like validations on items.
Leave a Reply