Tag Info

New answers tagged

0

I think that it is important to understand the difference between testing and QA. There is one post you need to read on the topic by Michael Bolton, Testers get out of the QA business. The short version is that testers, who don't change code, are assisting with quality, not assuring it.


0

Have you looked into using cucumber to organize your tests? Or just using a unit test framework like JUnit? My automation is in C# stack, and we use specflow to organize our tests which is pretty nice.


1

I want to share more general answer to this question. An absolutely must-have book which should be read by anyone touching the topic of designing the architecture of automated testing framework (regardless to programming language) is Experiences of Test Automation: Case Studies of Software Test Automation by Dorothy Graham and Mark Fewster. Based on real ...


-1

It depends on your language, and building tools choices. For Selenium, look into the PageObject model. That pattern will provide you with a very good starter point about how to structure and group your test cases. Building a framework is indeed, not an easy task. You have to have an eye for the future of what you would like to achieve and how far do you ...


0

TL;DR: How to minimize maintenance - short summaries of best practices. Best way is to create test suite for an application. Abstract out generic parts. Then try to use generic parts on different test suite, and generalize what you need to. After three apps, you have a base for framework - you separated generic parts from specific parts. Another option is ...


1

This looks like a position description for automated testing, which means writing automation code to run tests against the company's software. It's possible in your area there's a bigger emphasis on automation than I'm accustomed to, along with the understanding that good test automation requires programming skill. This is a good thing, especially if, as ...


1

A typical job-post for a testing position. This job description seems to be describing someone who has more programmatic and automation experience than someone with testing experience. That's not to say the best person for this job won't have both, but the JD seems to focus on desired automation skills. I can't comment on this being "typical" of job ...


1

My question is, why do so many (nearly 90%) job lists post programming as a requirement? Without speaking to every job poster, this question is not answerable. I would guess that it's because test automation is more in vogue than manual testing, based on my on experiences of testing scalability. I can only assume others have come to the same conclusion ...


3

Most automated testing frameworks require the user to either write in scripting language or in an actual programming language. Thus test automation equals writing code to run tests against the application. Maybe some frameworks work fully with recording the tests, but experience learns that recorded tests are harder to maintain. As an automated test ...


1

Position is test automation, not manual testing. So obviously programming is required. You will NOT be developing production code, but automated test. You need different skill set from a developer, use different tools for different goals, use different design patterns, need different communication skills, because you will encounter different problems than ...



Top 50 recent answers are included