- September 23, 2014 at 8:32 pm #4237
Hoping there are some folks out there that can share experience – I’ve just read through this developerWorks article; https://www.ibm.com/developerworks/library/j-test/
There’s a concept outlined in the article that suggests automated UI testing should be incorporated into the development process and that ‘ideally, the concept of a functional testing group should disappear’. Are there teams/organisations that you know of that have already embraced this practice, tasking development groups with the creation of both unit test and automated UI tests ?
I’d be interested to read your opinions on this topic and learn from your experience !
Ronan.September 29, 2014 at 7:20 am #4400
Did you link the right article?September 30, 2014 at 8:37 am #4428
Yes I think you mislinked the article. Do you mean to say the website UI testing? We have implemented this practice of Web UI comparison with our own tool TestingWhiz.October 1, 2014 at 8:47 am #4453
I think the right article is linked. It’s about how unit and functional tests are similar and that they don’t have to be done by separate groups of people. I found the article really interesting, but don’t have experience with this to share.October 1, 2014 at 9:58 pm #4497
Thanks Lada – you’re right, the link in my initial post is correct. Glad you found the article interesting and also that you got the point ! I’ve since spoke with some teams inside my own organisation who have adopted the approach of development teams owning both the unit and UI automation tests for a delivery. In reality, it’s not the developers who write the UI automation tests, but specialist testers embedded inside a multi-disciplinary delivery team (aka scrum teams). As such, the concept of the functional test group does disappear, but the functional tester lives on, albeit working in a focussed automation role !
Again, I’d be keen to understand others experience here.
You must be logged in to reply to this topic.