Mel's Thoughts: AB Testing Podcast #60


  "If you rely only on your eyes, 
your other senses weaken."
― Frank Herbert, Dune

If you haven't heard this specific podcast episode yet, you as a tester, as a developer, as an anything in the software development lifecycle, need to go listen to it.

Alan and Brent are definitely on the right track with this podcast. I have been shifting towards these things they discuss, like using analytics to test data, features, and getting to the root of the what the customer wants.

Customizable interfaces that machines build for people instead of people building specific tools. I've mentioned before that I don't think we will really have GUIs in the next 10 years. With the take over of voice user interfaces, and more APIs being made available in the public domain, the shift will come to the point that businesses will be about serving up information, they won't be able creating log-in features or displaying content. All of that will be scrapped, captured, and optimized by the user and served up however they would like it.

Annoyed with too many graphics, want all text - done.
Think text is too much, you want it to be audio read - no problem.
Want to chat with someone and want video and screen sharing as options - easy.

We are so close to this already. We'll start seeing macro packages that include the ability to enable a login for content. We'll see more integration between apps to where they won't be separate apps, but present as one seamless interface presenting the user features as they see or need them.

This is basically what AB Testing #60 is talking about.

I've touched on similar trends in this blog as well.


Road Bumps To The Bright Testing Future
I think where we will hit some stumbling blocks isn't having testers with creative approaches or ideas as to how to test the application or learn new ways of testing, it will ultimately be a couple of things:

1) Companies lacking a mature development process. They are already unsure about what testers can do for them and we as part of the industry are not making it clear enough.

2) Defining value of being an analyst tester rather than a quality analyst. Start shifting the job to be more systems analyst and less about functional testing.

3) Getting past the idea of what people think you should be doing and defining your job for you.  It's imperative that analysts become better influencers. We'll need to start doing a better job of presenting data to back up issues we are seeing. We'll need to pair more and work with developers to guide them on the tests that need to be written. We'll need to understand analytics, how they are created, what they mean, and where they are lacking. We'll need to understand more about the ecosystem of the software and hardware and focus less on the functional.
"Evolution is a light illuminating all facts, 
a curve that all lines must follow." 
Pierre Teilhard de Chardin

Comments

Post a Comment

Most Read Posts

Ready, Tester One? *GO!*

"I handed my passport to the immigration officer, and he looked at it and looked at me and said, 'What are you?'" - Grace Hopper (60 Minutes Interview) The Grace Hopper quote above always makes me think about my job as a tester. Companies that develop software know they need testers, but they generally have hard time figuring out what testers are and what skills they need in the role. There have many discussions about how testers can be more technical and at some point, coding comes up in the conversation. My response on twitter contained a few things on a list I have, which I created for a client, so they could have a checklist of skills. This checklist was a guideline to determine the skill level of the tester applicant. This is by no means a complete list and I would be open to additions to the list. Feel free to add those to the comments or tweet them to me. For clarity, I took the list of skills I had and broke them into levels. I like games and I lik...
Read more

Learning From Failure: The Tricky iOS Environment

"You build on failure. You use it as a stepping stone. Close the door on the past. You don't try to forget the mistakes, but you don't dwell on it. You don't let it have any of your energy, or any of your time, or any of your space."  - Johnny Cash There are times when our work, as a team, as testers on a team can give us insight into how we can improve things for the overall success of the product. Often those things are issues or defects which can present themselves at the most inconvenient times, in the most inconsistent ways. When we can learn from them and improve things for everyone on the team, the team benefits. When the team owns the defects and the testing strategy, not only the testers, then customers benefit as well. I was working remotely verifying a release and only had simulators and emulators to work with as I was testing mobile builds. Often folks mistrust builds which only use emulated software and not real devices for fairly good reasons...
Read more

Postman In The Pipeline: Newman Delivers

Image
  It's not me, it's the songs.  I'm just the postman,  I deliver the songs....  - Bob Dylan Recently, I've had the chance to work on a project with some other awesome folks which has involved creating a BFF - A back end for front end service. This allows the app to access several API and aggregate calls into something the app can use, or lets the app send information to the BFF for several APIs to receive. Part of the code coverage for the BFF was creating some simple tests with Postman around the business logic and interactions. Learning About Postman I did lots of reading. Lots of reading how others has done things (Danny Danton - big props for being a super help!). Eventually, I came down to a small set of tests which could give us some accuracy about our BFF pipeline and the APIs we were accessing with it. Postman has a couple of options for this, global variables, environmental variables, and plain variables. One of the first problems I came acros...
Read more