Tag Info

Hot answers tagged

8

Extending and maintaining automated tests costs time, but if your team are slaves to updating tests you are doing it wrong. :) One of the biggest reasons to create automated test coverage is to create a fast feedback cycle loop. Letting the test-team fix the tests afterwards slows down this process and will always lag behind. There is a high risk the tests ...


4

Why either/or? Work as a team with testers providing test ideas and expertise that the devs can code up. I would also shy away from an emphasis on GUI automation and get the devs working at a unit/system level unless they are doing this already


4

Here's how I would approach this kind of situation: Unit tests - Evangelize the living daylights out of unit testing. Any kind of business logic automation should be handled by unit tests, as should any other automated tests whose goal is to check the functionality of a single unit of code. This is developer-level code, but tester guidance is essential if ...


2

It depends on what sort of resources you can afford. Test Automation, done well, is not a part time effort. If you can't afford to have a Toolsmith on your team to work on the Automation Framework you will need help, or expect it to take a long time, or expect it to take effort to keep it going as it gets reprioritized. While most Testers do not spend a ...


2

I have seen this sort of thing before and the problem ended up being in how the page was coded: onmouseover vs onchange in our case. You may want to look at the the javascript events for the page, as it sounds very possible that the human interaction is causing some method to run whereas the web driver is changing objects in the DOM, and allowing web driver ...


2

While working on several projects I've described the following procedure to install Appium: Download Android SDK https://developer.android.com/sdk/index.html Extract Android SDK to /usr/local/adt/ unzip -qo adt-bundle-*.zip -d /usr/local/adt Set ANDROID_HOME and JAVA_HOME environment variables export JAVA_HOME=$(/usr/libexec/java_home) export ...


2

Coverage is always coverage related to some model. This often gets skipped over, which leads to much confusion "you said you had 100% coverage so how come there's a bug?!" When you're looking at unit tests, then it's possible to use code coverage as an indicator (there are tools that can measure what percentage of the lines in your code are exercised when ...


2

The most efficient tool for testing the appearance of a website is still the human eye and brain. That said, if you want or need to automate, image comparison is probably the least effective method because even with fuzzy logic it can generate far too many false positives. All it takes is a change in hardware (a different monitor or video card - this will ...


1

In your test environment, you need your developers to enable some way of bypassing the captcha. You need to make sure that is only available in your test environment. There are a lot of ways of doing it, commonly it is you typing in a specific string that is recognized by the system to bypass it.


1

I think you should be able to use JaCoCo to gather coverage of the backend, but there are more coverage tools for Java see: http://en.wikipedia.org/wiki/Java_Code_Coverage_Tools Process looks something like this: Start application with coverage tool enabled Run tests against web-app instance Generate report of coverage files See this article about ...


1

TL;DR: Neither. Use ID or name. I strongly disagree with @Jon Duffy. If your CSS designers are up to snuff, they will create custom class names for the elements, so even if elements are moved around (XPATH changes), the class name itself stays the same. Even if CSS classes have different definitions, the name itself is the same. Also, location by CSS is ...


1

Been the manual QA, moved to automation over 15 years ago. Can now code in Java, C#, C, Python, etc, etc... written automation tests in more tools/languages than I care to remember. Trust me when I say learn Python and WebDriver. You will be productive with this combination faster than any other, and since you are learning as you go, your employer will ...


1

Although I have never used them, it seems Unity released their own set of testing tools. See their introduction blogpost: http://blogs.unity3d.com/2013/12/18/unity-test-tools-released/ See their examples: http://blogs.unity3d.com/2014/05/21/unit-testing-part-1-unit-tests-by-the-book/ Get it from the Asset store: ...


1

Approach 1 Create a class, for example Hull. In the cass is a protected variable WebDriver driver. In the class is a method setup() with a @Before annotation. In the method you has a condition: Is WebDriver null, initialize; else do nothing. Classes with test cases extends from Hull. Classes with test cases can use the variable driver. Approach 2 ...


1

I have to disagree with Twaldigas on point three: 3.) I understand the concept of creating scripts to perform tasks, but I've read re-creating my manual tests as scripts isn't the direction I should be headed. What types of tasks should I be looking at to automate? You should automate manual tests. First of all automate the regression tests. ...


1

As user246 says, whether you automate your permissions tests depends on the application and whether it can be properly tested that way. The question of what you test and how always depends on the application, its user base, and how critical each feature is to that user base. There are no best practices. This is something that a lot of people find difficult ...



Only top voted, non community-wiki answers of a minimum length are eligible