30 Days of Automation in Testing Day 3: Explore "The Club" and Contribute

[rk_manne (Ramakrishna)]

Day 3 - #30daytestingchallenge

Challenge - Explore the automation thread on The Club and contribute to the conversation

Contributed to this thread today

Getting started with the basics of automation code (edited)

[qakumarnz (Kumar)]

Tried to address one the common issues faced by new automation testers in this link: Exception when clicking on an element
Exception when clicking an element, Unable to find a element, Can’t find the locator, Unable to find the locator value – Generally, all these exceptions can be handled by implementing anyone of the below solutions.

1. Check your locator value again
2. Use different locator to identify the web element
3. Your driver might be trying to find the element before it is ready, so use appropriate waits

You can also check this here: https://qakumar.wordpress.com/2018/07/04/day-3-the-club-interaction/

[paulmaxwellwalters (Paul)]

I contributed to that thread as well.

[vic (Trung)]

Day 3 - #30daytestingchallenge

Challenge - Explore the automation thread on The Club and contribute to the conversation

Contributed to below threads:

Getting started with the basics of automation code

Hi all. I’ve been a tester for a few years now and want to dip my toes into automation. There are a few opportunities to build some scripts where I am currently (using Protractor) but I have very little experience in programming skills. I therefore feel I want to start with the basic concepts and learn to walk before I run. I hear terms like “objects” and “elements” thrown around for example but I have little concept of what they are to a language to consider adding them into a piece of code…

How do you measure automation success?

Hi Ali, This is a good question when doing automation testing. Below are some criterials to measure automation success based on my experience: The framework is clear/logic/easy to use and enough power to catch log/result/reports, can integrate to other CI tools, ex: jenkins… The stable of written scripts The scope of automation testing? ( how many percents TCs automated? how scale the automation TCs covered?) Performance of automation test suite? (how long does it takes to run?, how much ti…

[dkotschessa (David)]

I contributed to the thread “What To Automate.”

What to automate?

Since I’m new to this , I’m going to quote someone wiser than me but who I agree with. I have been reading Alan Page’s book, which is more “automation philosophy” than a technical book. But I really like what he says here, because it jive with how i got interested in automation - not just automated testing, but all around task automation: Good testers test first – or at the very least they think of tests first. I think great testers (or at least the testers I consider great) first think abo…

[karishma]

#Day 3 : I contributed to thread Setting up Test Cases

[mae (Margot)]

I’m a little bit behind on the challenge
For day #3 I’ve just contributed to “Getting started with the basics of automation code”.

Getting started with the basics of automation code

I guess it depends on what technologies you want to start using. I would suggest if you are currently working for a company which implements automation testing, start with those technologies. If they are flexible someone might show you around their framework or even let you check in a few simple tests to begin with while you are learning, if you have a friend there they could review your code. I’m currently reading Java for Testers by Alan Richardson, which is a good place to get started. From …

[pabs616 (Pablo)]

Totally new to this challenge (as I’ve transitioned to QA Automation since last year) and have found so many new and exciting opportunities. I’m kind of fast-tracking my progress, knocking out “days” in small batches due to limited bandwidth and what-not. The best, funnest things I’ve come to love about my engineering role is the challenge of always learning something new, on-the-fly.

Case in point: at a recent project, knowing little about Javascript, I was introduce to a test framework - codeceptjs - which was a little overwhelming at first since I was experienced with JAVA and PYTHON. But in a matter of a week, and with the help of the Developer who introduced it to me, I was up and running with a successful E2E test.

I’m still working through PYTHON as it was the language I have been teaching myself. But I’ve been exposed to proprietary frameworks, custom frameworks, and most recently KATALON - a superb out-of-the-box framework that has surpassed a lot of testing issue I’ve had with others. And lord knows, I’ve researched just about all the best ones.

In conclusion, for the next 30 days, I will be consistently active in posting my findings here … as well as on my blog which I will only promote this one time - http://severeqa.blogspot.com/. This was dedicated primarily to QA, as a round-table to discuss things not-always about testing, but has since shifted to Information / Cybersecurity – my passion.

30 Day automation challenge accepted!!

[helena21 (Helen)]

I have contributed to this topic : Automated testing for Windows desktop

[youngdq232 (Quang Le)]

Day 3
Challenge - Explore the automation thread on The Club and contribute to the conversation

Contributed to below threads:

Getting started with the basics of automation code

I guess it depends on what technologies you want to start using. I would suggest if you are currently working for a company which implements automation testing, start with those technologies. If they are flexible someone might show you around their framework or even let you check in a few simple tests to begin with while you are learning, if you have a friend there they could review your code. I’m currently reading Java for Testers by Alan Richardson, which is a good place to get started. From …

How do you measure automation success?

Hi all, This is a regular question and always be asked by the client frequently Below are some ideas to measure automation success based on my experience: We should analyze, estimate the automation difficult thing and the risk of your project. After that, you will have the number of test cases can be covered as much as possible by automation. I worked on some projects that the coverage was about 50%, and the others should be 90% or 100%. But all are successful. It’s depending on the project…

[joaofarias (João Farias)]

Three threads

Where would you start with automation in a micro services environment?

I thought in suggesting this same document Russel. As Martin Fowler himself says, architecture is the shared understanding of how things work. Communication is necessary for good architecture understanding. If we are in a well-known context, we can even move further with bad communication. However, when in enter in uncharted/complex territory, this understanding is necessary. Therefore, before thinking in tool X or strategy Y, I would think if the communication is effective: “Do I understa…

Automating the comparison of text files

Unix itself has a diff command: https://www.networkworld.com/article/2696092/operating-systems/unix---having-fun-with-diff.html And, naturally, you can chain the output into other Unix commands and do all kind of magic.

When should acceptance criteria be converted into automated tests

I would be with Uncle Bob (in “The Programmer’s Oath”) on this one: “3 - I will produce, with each release, a quick, sure, and repeatable proof that every element of the code works as it should.”. If the changes are generally well cover by non-business tests (unit, integration and component) and few bugs escape, one could postpone the “repeatable proof of work” to after the production code. Otherwise, for any reason, I would suggest that programmers take care of delivering them together with t…

[kohavn (Khoa Koha)]

Thanks all your guys for the information.
This forum is extremely useful.