Feedback

I have been trying to switch from being a manual QA Engineer to an automated tester for years. Back in March 2015, finally, I found a position at Fitbit-Boston! With the new job, I had been trying to capture as much knowledge as possible. Blogging about what I was learning, I found, to helped stick the information in my head. I've done it ever since.

Here are some kind words I have seen around the internet, referring to this blog:

Angie Jones, SDET at Twitter, during her talk "How to Become an Automation Engineer" when she mentions automation gurus to follow on Twitter (12/11/2017)
"T.J... T.J. is very interesting, especially for people who are new and trying to transition into automation. He did manual testing for about twenty years, and then he transitioned into automation, and so he's been learning a lot on his own.  
"What's great about T.J. is that he documents all of these things that he's learning. And he has a web site. And he goes step-by-step on 'Okay, I'm picking up this new tool or this new technique, and here are things you can learn about it' ... So... things that I haven't used before, I can go to T.J.'s site and learn from him". 
Alex McPeak, in the article "Expert Insight: Why Testing Matters" on the CrossBrowserTesting.com, quoted a story I relayed to them (12/11/2017):
"The team developing a new European Union shopping cart found out quickly that the VAT tax test server was flaky. But was that the cause of the one-cent discrepancy between the estimated and actual price that randomly appeared? Everyone on the team thought so. I wasn’t sure. 
"Taking my Selenium script that placed an EU order, I looped it twenty times, collecting data all the while. It had a failure rate of 40 – 60%. After showing the metrics gathered to the new developer assigned to the EU cart, he checked his code. It turned out he had made a rounding error calculating the estimated and actual tax differently. 
"Does something not feel right? Don’t just go with a hunch or a gut feeling. Make sure to do the legwork required."

Mark Winteringham (aka 2bittester) on his blog MW Test Consultancy used a blog article I wrote to add to the virtual conversation I started with "Code coverage and automated checks: Is 100% coverage enough?" (8/21/2017)
"Recently TJ Maher (@tjmaher1) posted some great questions in his article “Are unit tests and 100% code coverage enough?”. Questions that we should be asking ourselves in regards to Continuous Development and DevOps. There was one question that jumped out at me. And it’s a question I find myself challenging a lot when it comes to automated checking.
‘Do you think 100% code coverage of unit tests and integration tests is enough in environments using Continuous Deployment? What do you use as supplements in your testing efforts?’
"The discussion and pursuit of 100% code coverage with automated checks are nothing new. But, as continuous deployment’s goal is to enable teams to release regular, small releases and adopting a testing first culture. And Automated checks have taken on a more vital role. It’s important to scrutinise automated checks more and ask: 
"What is the role of automated checks in helping us understand what sort of product we are actually releasing? What are the weaknesses of automated checks? [...]" Read More


Alan Richardson on Quora.com referred to me and this blog, answering the question, Can the manual QA become a good automation QA with Java and Selenium? (July14, 2017)


https://www.quora.com/Can-the-manual-QA-becomes-a-good-automation-QA-with-Java-and-Selenium/answer/Alan-Richardson-13


Alan Richardson, How to Improve Your Software Testing (July 7, 2017)
"[...] I continually try to seek out practitioners that I can learn from. When I see an expert, I look to see if they have left a trail of evidence that I can study and learn from. I don’t just want their conclusions, I also want to see their working, as I can learn from that.
"Recently I’ve been following the work of the following practitioners on GitHub because they are leaving a trail of evidence that I can learn from: Bas Djikstra, Mark Winteringham, Angie Jones, TJ Maher [...]
"I like to find practitioners who are leaving a trail of ‘working’, not just explained results, but processes, code, ‘doing’ videos, case studies. I think this add longer term study value than an outcome report.

"And study their work because they may be working at an aspirational level - a level of competence that you have not yet achieved, but they demonstrate the possibility of achievement and you can learn from them to build the skill to do what they do, or take a different implementation path after learning from their experience (a path you then document for future practitioners)".


Alex McPeak, "What’s the Best Programming Language to Learn First? It Depends" from the CrossBrowserTesting Blog (April 18, 2017)
"[...] Especially for testers, as the QA industry begins to increasingly require skills in automation, programming knowledge becomes an invaluable asset. In 'Coding is key to a test automation career: Are you prepared?' T.J. Maher advances that learning to code is the number one way to break into test automation. Then, even after you think you understand it, you need to continue practicing all the time. 
“ 'The most important thing is not to stop practicing to code once you’re hired as a test automation engineer,' said Maher. 'Learning is a never-ending journey.' ”


John Ferguson Smart, creator of the automation framework Serenity BDD (March 29, 2017)


Brett Tramposh, Quality Practice Leader, How to Add Test Automation to your Quality Assurance Toolbelt (January 26, 2017)
  • Information gathered from my blog and other articles used in Powerpoint presentation. 
  • My TechBeacon articles are listed under Brett's "References" page. 
  • According to Brett, "This was a discussion at our Rose City SQE Meetup group on January 25th, 2017. Great conversations and ideas on how to foster a better culture in growing our engineers into the skill set they need to compete".

TechBeacon: Mitch Pronschinske, 7 DevOps trends to watch in 2017 (January 12, 2017)

I must have been in a real foul mood that day when I gave this quote:

"Testers will learn to code or perish

"TJ Maher, an automation developer and TechBeacon contributor, spent the last two years updating his skills to move from manual tester to automation developer to software engineer in test. In those same two years, he’s seen many of his former QA testing colleagues lose their jobs due to the major changes going on in the testing industry right now.
“Continuous integration and continuous delivery turned the big splash of Selenium WebDriver into a tsunami that washed away almost all of the software testing industry, drowning many of the manual testers and eroding their base of employability.” —TJ Maher
"For many testing engineers, 2016's motto was 'learn to code or perish.' Testing is now focused at the web services level, with tremendous demand for RESTful APIs, and Selenium wrappers, he says".


VeritechIT: Best Blogs 2017:  Best IT Blogs 2017: Must-Read Resources for CIOs, IT & Security Pros (January 3, 2017)
"TJ Maher has worked in the software testing field since 1996, and since 2015, he’s also been an automation developer and blogger. He started Adventures in Automation in 2015, initially as a way to store the 'copious amounts of notes' he found himself taking when he began interviewing for automated development positions. At Adventures in Automation, you’ll find posts on topics ranging from automated testing frameworks to security testing and software quality assurance.
"Three posts we like from Adventures in Automation:


EvilTester.com, blog: How to improve your CV and improve your chances of finding your next software testing job, (12/07/2016)



PetriKainulainen.netJava Testing Weekly 47 / 2016, (11/21/2016)

Tadhg88: Postman Intro (8/10/2016):

  • The author, Tadhg88, writes to his readers about how to use Postman, referencing my blog. 

PetriKainulainen.netJava Testing Weekly 17 / 2016, (4/25/2016)
"Why Use a Builder Pattern? Examples of Telescoping Constructors: when storing Address data identifies the problems caused by the telescoping constructor (anti)pattern, and describes how you can solve them by using the builder pattern. I think that the builder pattern is extremely useful tool for creating test data, but you shouldn’t overuse it because it is not free".

Alan Richardson, EvilTester.com (4/12/2016)

MrSlavcheck.com: "Kick Ass Blog Posts" (2/15/2016)

"Another great post by T.J. Maher, on his blog post related to the all famous testing pyramid and the different proportions that types of tests have in it, definitely a read you would like to take a look into:
Testing Beyond the UI: The Testing Pyramid Problems with UI Tests".


TestingCurator, Matt Hutchinson: (1/23/2016)
PetriKainulainen.netJava Testing Weekly 3 (1/18/2016)
"Automate Amazon: Writing a Shopping Cart Test is the latest part of T.J. Maher’s Automate Amazon tutorial. It explains how you can write a test which ensures that Amazon.com preserves the prize of a product that is added into a shopping cart. This means that the prize shown on the review shopping cart page must be the same as the prize shown on the product page. By the way, this post assumes that you have read the earlier parts of this tutorial".

Joe Colantonio, TestTalks.com (1/17/2016)
TestingCurator, Matt Hutchinson: (1/16/2016)


MrSlavcheck.com: "Kick ass blog posts" (1/11/2016)
"This guy deserves applause for the hard work he has done on writing a whole automation framework for ordering in Amazon, in order to show how it looks all together. The article is part of a series, I strongly recommend you reading all of them if you want to know how all the little pieces in automation are tied together, really good read". ( Re: Automate Amazon: Initializing Login and Cart ) 
PetriKainulainen.net: Java Testing Weekly 2 (1/11/2016)
"Automate Amazon: ProductEnums and ProductObjects is the fifth part of T.J. Maher’s Automate Amazon tutorial, and it describes how you write Selenium tests which ensure that you can add products into your shopping cart. This post provides good advice on linking the persisted test data with your test cases. If you are not already using enums for this purpose, take a look at this blog post".

Alan Richardson: (1/7/2015)
PetriKainulainen.net: Java Testing Weekly 1 (1/04/2016)
"Automate Amazon: Writing a Sign In Test  describes how you can write a Selenium test for the sign in function of Amazon.com. This is a very good post because it basically explains everything that is required to test the sign in function. Also, you should read the other parts of this tutorial as well".
BizTalk: 50 Must-Read IT Blogs 2015 (12/10/2015)

"The life of a QA specialist isn't easy. But automation can help make the processes easier. Software quality-assurance engineer Thomas Maher Jr. catalogs his adventures with automation and offers QA best practices and insights for companies that do software development. 
"MUST-READ POST: This post, which raises the question of whether QA departments should include dedicated automation teams. 

"Follow: @tjmaher1 | Read the blog: adventuresinautomation.blogspot.com"




Neotys Blog: Testing Roundup (10-06-2015)
"Thomas F. Maher, Jr has been a Software Quality Assurance Engineer for over fifteen years, and is attempting to make the leap from manual to automated testing. Recently, he posted an article to his Adventures in Automation blog in which he discusses the evolving role of QA Engineers—an evolution that directly relates to the increasing speed of software projects. 
Test automation dominates the industry, and as a result, many may question the necessity of QA Engineers: “If you can replace some of the tasks a QA Engineer does, why not replace all of them?” 
Maher Jr notes that his organization maintains a healthy mix of both manual and automated QA, an ideal structure in his opinion. Read his article  for a closer look at the shifting role of QA Engineers and then decide for yourself: are QA Engineers really going extinct?"
Post a Comment