Tag Info

Hot answers tagged

5

The short version: Don't sweat on automation or test cases. Chances are you won't get time to build it because there's too much that has to be manually tested now. Instead focus on building light-weight, easy to maintain documentation of the key elements of the software you're testing. The longer version: This is my world. I'm the sole tester in a team of ...


4

Here's how I'd approach this situation (the tl;dr version): Analyze your options and give an indication of the risks involved. Your risk analysis should show your preferred option as having the lowest risk (expressed as a relative number, e.g. 1 being the highest risk and 25 the lowest) and state a few of the biggest risk factors for each potential ...


3

I got the same issue when I use Firefox 39 with Selenium 2.45. After that I upgraded to Selenium 2.46 and the issue got resolved. I think that the problem is the Firefox and Selenium version agreement. Note: the default setting will make the Firefox update automatically.


3

When is a good time to develop new automated test, and who should be responsible for this? Developing the structure of the automation can begin very early on in the process. Once the requirements are set the objects can start getting built out, be put into classes and a lot of the assertions can be built that way all that remains is ToDos that hook ...


3

My recommendation would be to build an automation suite, on the base of the product. Then, to have your testers manually test the differences in the product based off of your client requirements. Unless you hire other testing resources, automation will do a lot of the testing for you, in the base product.


2

We are currently in a similar situation, except not with Selenium, but with CodedUI. I think for the concept the technology does not really matter. We have defined a critical path with functional locations that are most critical to our application. This because we have nearly no automated test coverage and want to start with the most important parts first, ...


2

The most popular tools are listed below: JMeter Gatling Grinder Tsung Yandex.Tank HP LoadRunner NeoLoad Here are few comparisons of them: Grinder vs Gatling vs Tsung vs JMeter LoadRunner vs Grinder vs JMeter Loadrunner vs JMeter vs NeoLoad For more comprehensive list of tools also look at www.opensourcetesting.org.


2

To start with, there is no formally defined list of standard test methodologies. That said, there are a number of test methods that are better suited to web applications than desktop applications: HTML validation - even if a desktop uses HTML display in some or all of its screens, it's not going to be as accessible as right-click - view source in any ...


2

I had the exact same questions as you when I started the "testing" compartment in my current Agile project. It is indeed not feasible to write and maintain test cases in the tradition format. User stories are delivered every few weeks, and change rapidly afterwards. Test cases would become obsolete faster than you can write them. One approach that I found ...


2

To start with, I'd suggest browsing the answers of the questions showing as related, particularly Test Automation in Agile? and Agile Tester vs Traditional Tester...........? As far as test case writing, it doesn't really matter how you handle that, as long as someone who is moderately familiar with the application can follow your test cases. The main ...


2

Ouch. No, the old school sort of test plan doesn't make much sense in your context. The only reason I can see for doing them is if you had a contractual requirement with a client to deliver them. Will anyone read them except you? (If no - then stop doing them now!) If you re-read them, what do you use them for? To remind you of how to do something (is it ...


2

Telerik's Test Studio is also a good tool and will provide you required support and features. You can use this tool for testing Web, Mobile, Desktop (but only WPF) applications. test Complete is also a good tool which will suffice your requirements (advantage is it supports more variety of Desktop applications). Again, cost wise Test Studio is cheaper than ...


2

Appium would probably fit the bill. It uses the iOS simulator (comes with XCode) to run Selenium tests. For Android it uses the Android SDK (comes with Android Studio).


2

You can capture the server utilization by yourself too either use the Jmeter plugin http://jmeter-plugins.org/wiki/StandardSet/ this will provide you the CPU, Memory, Network I/O etc. utilization of the server and then you can check whether any of these things are creating bottleneck for you. may be you will find that on increasing the number of users ...


1

Good you found a bottleneck, now as with all automated test failures you can question, is it the test, the code or the infrastructure. We cannot answer your situation for you. I would advice to have a developer and a server-admin nearby when performing load tests. The server-admin should monitor and configure the infrastructure and when the infrastructure ...


1

As always, it depends. If the application developers have been building unit and integration automation that runs with each build, you aren't as far behind as you would be if no low-level automated checks existed. QA is usually in charge of automated GUI checks and may also be in charge of some of the high-level headless automated checks (such as API ...


1

Usually developers write unit tests (because unit tests are close to the code developers know well). Automated GUI test use different instrumentation (Selenium?) so need a bit different skillset. Sometimes might be even developed in different language: because GUI tests are inherently slower, it might make sense to use language like Python which allows you ...


1

IMHO investing in a transition to a standardized results storage in a database will pay off big time in the long run: changes to script output would only require matching changes in the method of normalizing the results before storing them in the DB validating results would become simple comparisons between standard DB field values easy to handle various ...


1

Kate is dead-on with her suggestion about the short version. If you are REALLY pressed for time, these are the steps I take: You want to save your team time and pain, and you do that by focusing on potential issues that are going to be much less costly if we catch them sooner rather than later. I usually start by asking myself "what feature(s), if broken ...


1

Common UI testing tools (Appium and others) will answer most of your requirements except for Video starts Playing This is tricky and can be achieved to some degree depending on the level of confidence you require. The simplest solution is using the UI tool to get a few screenshots spaced in time, than compare them to each other (verifying that they ...


1

The first three things that come to my mind are: Can you get the product owner to test new functionality? As they know what they want (as opposed to what they asked for) Don't have a test plan, have a one page check list that you can print off and tick off, just so you don't forget any major areas of functionality. Start automating simple things, and ...


1

As your building Windows desktop applications have you looked at what MS has to offer? I think their Lab Management tools are designed for these challenges. Combined with TFS build server its should be able to bootstrap an test environments on the fly for each build and test run. And here an article about combining TFS, Lab Management and CodedUI: ...


1

It seems to me that having Acceptance Tests is a must have, and possibly testing sessions for bugs...but I'm wondering if the old school type of test plan....really make sense? Acceptance tests are based on a ticket's Acceptance Criteria. A testing session for bugs... I think you mean a smoke test. Which I advice before every deployment, at a minimum. ...


1

Both Acceptance tests and Integration tests could be either manual or automated. Unit tests make sense ONLY automated, and I assume your developers write unit tests (as they should). Start with manual testing most often used and most recently changed functionality first, where detecting a problems has best value for time invested. But ask your manager for ...


1

Some tests are better run via a test API as they can then test sections of code that may be unreachable or very hard to reach but a test API does not test the database interface so you also need to test with SQL. The most important thing to remember is Never, Ever, run untested code on a live database - you could potentially do an immense amount of damage ...


1

Telerik test studio - licensed iMacro Applitool - UI based automation (pxl to pxl verification, layout, content etc) Let me know if you need a help on above things.


1

Obviously automating everything is impossible... How do you think teams that practice continuous delivery are working? Being Agile means that you optimize the feedback cycle on all levels, for long running projects a rule of thumb should be to automate everything. This means the whole pipeline up-to deployment in production. I would rather say: ...


1

Your code logic seems okay but there are some parts which need to be changed. First when you want to search a non static value in dynamic id, searched value should match correct pattern so your pattern can not find expected span , this code line should be changed to "By.CssSelector("span[id^='-chosen-']"));" //comment : I hope there is not any span which ...


1

You are on the right track. I used to do the granular test plans until relatively recently. I have gone the direction of making a Test Plan mostly consisting of User Stories. You need to remember your audience when writing anything. My Test Plans are part of the deliverable to clients so it makes the most sense that anyone can read it and use it. That means ...


1

You can use BadBoy WatiR or WatiN (it has WaitN test recorder and supports IE 6, 7, 8 & 9 and Firefox 2.x & 3.x) tools too for testing Web UI. But, are you looking for free tools only? There are number of paid tools which provide multiple browser support and very easy to use and implement. But again you have to discuss this thing first within ...



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