I love all of this and bonus points for mentioning Notion.
I'm often advocating our customers decouple things like their UI from their functional tests, or add unique selectors, and having it all in a list is chef's kiss. I think the biggest challenge for teams where the QA folks aren't empowered to influence design is they miss out on all of these advantages.
It's also weird being a former Ruby developer where a lot of the test admin stuff was taken for granted, and now parts of the JS and SDET community are having to re-discover them.
Thanks and 100% agree. The way Devs should be able to contribute to the test scripts should be the same as the QA's being empowered to contribute to the codebase (e.g. adding unique selectors, etc.). It all boils down to collaboration. It's hard to break the stigma of devs and QA's pushing back and forth with who's going to do what.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
MAAAAAAAAAAAATE. Noice.
I love all of this and bonus points for mentioning Notion.
I'm often advocating our customers decouple things like their UI from their functional tests, or add unique selectors, and having it all in a list is chef's kiss. I think the biggest challenge for teams where the QA folks aren't empowered to influence design is they miss out on all of these advantages.
It's also weird being a former Ruby developer where a lot of the test admin stuff was taken for granted, and now parts of the JS and SDET community are having to re-discover them.
Thanks and 100% agree. The way Devs should be able to contribute to the test scripts should be the same as the QA's being empowered to contribute to the codebase (e.g. adding unique selectors, etc.). It all boils down to collaboration. It's hard to break the stigma of devs and QA's pushing back and forth with who's going to do what.