I have had about 4 QA automation jobs, about 10 interviews, and was on the other side of the interview table about 10 times.
QA Automation involves writing automated testing projects. These are software projects which can be very complex, often requiring:
Managing deployments of applications
Starting and stopping application servers
Setting up test data, ...
Rather than taking those specific principles and try to match up to them an alternative approach might be to focus on:
DRY - Making sure you don't repeat code unnecessarily
Readable - Use real english words and avoid most abbreviations
Simple - Use Single Responsibility to make sure a function does only 1 thing
Maintainable - Aim to make the code ...
What's going on here is that the company has decided that application engineers and automation engineers are both programmers and as such both roles need to know programming principles.
Notice for instance the tasks you list such as Palindrome, Prime Number, etc. are also programming tasks that the developers being hired will likely not actually do in their ...
I do not believe there could be some special advice for testers on how to use the OOP principles since as soon as you open your IDE and start writing code you stops being a tester and starts being a developer in test. However below is what my experience shows.
You are to use this principle in your tests to segregate public methods and fields ...
I once wrote a blog post on why it is hard to find technical testers who can program, and why candidates fail such technical interviews. We needed testers with developers' skills for two reasons:
Writing maintainable tests and test tools requires engineering skills. I have interviewed testers who claimed they can program, because they wrote Selenium scripts,...
What you call "automation testers" and "developers" are both the developers. Both of those two classes should understand basic concepts of the language they are going to use (what is often referred as core), both should think algorithmically effective and both should be aware of most popular architectural patterns.
The difference between "automation tester" ...
"A journey of a thousand miles begins with a single step"- Lao Tzu
Go Small .I would start with a known open source project- most likely an automation library which I am already using .
I would make a list of interesting API methods which I am using on daily basis and curious about how they work under the hood.
In this way I will take small baby steps to ...
also to add all above, the trend is shifting test to left which means testers /test involving earlier in development pace. Due this testers specially automation testers need to have knowledge of programming.
I have been in the test automation space for a few years. On one hand I would say a test automation project should be treated like any other Java project in terms of practices - you should use the available Java features so that you have a high quality software project at the end of the day. Here are aspects which I think are most important.
Maintenance is ...
OOP concept plays an important role in developing a well-structured test automation framework. Just sharing some simple examples of common OOP application in test automation. I am using Java and Selenium Webdriver in these examples.
Encapsulate the data of the web pages. Here, data means the elements of the page like texts, buttons etc.
Get in contact with the developers. Just like with internal projects you probably need someone to guide you through the code to get started. Larger Open-Source projects often have a IRC channel or a mailing-list.
If you are really intressted in helping the project and not just to understand their test-architecture you could send a message to a communication ...
You cannot concatenate JMeter Variables this way, in order to evaluate nested JMeter Variables you need to use __V() function like:
More information: Here’s What to Do to Combine Multiple JMeter Variables
Your issue is that the Object Repository has learned this object with a title or caption including the number (95) which increments.
The solution is to change the property in the Object Repository to a regular expression which will allow the title/caption to match on the parts which are static, so if you have
"Fax Order No. 95"
As your Title property for ...