One of the themes I talked about during my presentation in Wellington was the blurry line between test and development in a distributed environment like Automattic.
I was recently having trouble with a complex method in our WordPress.com e2e test page objects, so I used my skills as a developer and wrote a change to our user interface which adds a data attribute to the HTML element.
This meant our page object method immediately went from this:
Continue reading “The blurry line between test and development”
“Most of us are anxious pretty much all the time – but frequently imagine that other people aren’t. It’s time to admit the truth. Anxiety is just a basic fact about being human.”
~ Alain de Botton
We are all human, we are all worried and anxious pretty much all the time, people just don’t tell you that they are. We wear masks and we hide it well.
But why do we test like we’re not anxious or worried? Why don’t we test for real life?
Continue reading “Test for Real Life”
I recently embarked on writing some new automated end-to-end tests for an existing product that has been around for some time but has never had e2e automated tests written for it.
Continue reading “Make sure your end-to-end tests align with your company’s strategy”
Do you actively close bugs because they reach a certain age?
One of the (many) things I love about Automattic is the attention that is given to bug triage. Bug triage is the habit of continually grooming our bug lists to ensure they are constantly relevant, updated and reflective of the current state of our products. A benefit of this is that an up-to-date and prioritized bug list translates directly into a backlog of maintenance work items for a product development team.
Continue reading “Should you close old bugs?”
I recently saw this quote in an article by Nikita Hasis on Medium.
“If Your Test Leaders Aren’t Telling You To Write Code, They Are Lying!
Even if it’s by omission.
There’s this argument, almost daily, about whether software testers should learn programming. I’ll jump right in. It is unimaginable that someone would tell you NOT to learn something. That’s the first, and probably shittiest lie that inexperienced testers get fed. It’s further unimaginable, and downright irresponsible to tell people not to learn something that is very clearly where a large, well-paying, and above all interesting part of the industry is heading. Wanna work on innovative, data-driven projects with smart and driven people? You probably need to pull up terminal and at least get your toes wet, y’all.
The worst part of the lie is that it imposes that coding is a difficult grind and will only cause more problems than it solves. I even saw Alister Scott’s blog post referenced as an argument against coding, ironic as it is.”
~ Nikita Hasis (Medium)
Since Medium is a walled garden that doesn’t allow you to leave a comment without creating an account I’ll leave my response here instead (where anyone is free to comment however they like).
Continue reading “(Not) Lying about Writing Code”
Could you share us some automation testing channel that could help up update the news of testing trend also improve ourself for a better technical skill and problem solved
There’s an awesome blog/channel, right here on WordPress.com, that meets your needs perfectly, it’s called Five Blogs. So make sure you check it out and you can follow it for great frequent updates.