Tag Info

Hot answers tagged

4

That partially depends on what you want to automate. From the front page of SeleniumHQ (my highlighting): If you want to create quick bug reproduction scripts create scripts to aid in automation-aided exploratory testing Then you want to use Selenium IDE; a Firefox add-on that will do simple record-and-playback of interactions with ...


4

This problem hits everyone with a decent-sized application sooner or later. Some of the things you can do to help manage your test cases more cleanly: Use a self-documenting system - if you're coding Selenium with C#, use the MS XML commenting and something like Sandcastle to publish the documentation that's generated on build to a common site. That way ...


3

What you want is called an continuous integration (CI) server. A very popular one is called Jenkins (jenkins-ci.org), though there are others both open source and commercial. You can configure it to watch for checkins, and to build a project. If the build succeeds, it can trigger tests to be run. If the tests pass, you can trigger other jobs such as ...


3

Naming and separating out your reused parts (tests, keywords for maps). I call this "common" tests/maps. If you already have alot of tests automated then this will be more tedious, but pulling out your unique maps and naming them appropriately will identify the actual controls that are being duplicate tested. Test Naming conventions that follow the ...


3

Do not disable the tests, which fail because of known bugs. I would suggest to group the failing tests and run them in another test suite. You might use a group annotation on the tests for that, maybe "knownFailures" or so. The group annotation is better then a "link to issue" thing. Group annotations are supported by various test tools. Configure your ...


2

Try this , storing all the Web elements of Select list in a List and then getting its size. List<WebElement> optionCount = driver.findElements(By.xpath("//select/option")); System.out.println(optionCount.size()); Thanks.


2

One thing that is often overlooked is to make use of your coverage tool(s) for more than ensuring that every line of code gets tested - if you configure your tool to produce a separate named output file for each test/test sequence then you can quite easily scan these for lines/blocks that are being tested in more than one test. The other key point is - as ...


1

MS has several command line tools that will run tests. There's more information about how to use them and how to choose the tool you use on the MSDN site: http://msdn.microsoft.com/en-us/library/ms182486.aspx I'd suggest reading the documentation and experimenting with the different tools to decide which of the tools works best for your situation.


1

As Far As I Know and I use QTP 11 only. HP still don't provide proper support with WPF Controls. In some Cases I've seen people contacting HP and then getting some specific patch, I have not done it so can't comment on that. What I read and used and understood... If it is WPF and there is a QTP as a tool for automation, be ready to say NO or be ready for ...


1

After a lot of research,coding,trial and errors, I managed to build the infrastructure I envisioned. Essentially I wanted to build a small (very specific to my team's needs) scale of SauceLabs/Browserstack. @Sam Woods , Sauce is a great service but overpriced for our needs. Also,Browserstack provides features that we don't really need in it's light plans. ...


1

To comment on exactly how to write that...sure you can "code" whatever you want to code, but if you are looking for simplicity and repeatability with minimal work... I would recommend Sikuli as it will use image recognition so it won't matter what VM it is as long as it kicks it off the same way. It can also execute any test just like you would manually. ...


1

Here's the short rundown on TFS and the Microsoft application life cycle management ecosystem: TFS - Team Foundation Server is the "glue" that pulls everything together in a central repository. TFS can be used to manage builds (using MSBuild.exe), issues, test cases, automation, source control, and so forth. Visual Studio - As well as the code IDE, Visual ...


1

Suggestion: Every test automation shall run in a dedicated environment, dev code/script/db changes shall always auto deploy to this environment, automated test shall only run here. With such design the team can easily design the automated test an test data as well. After each success test execution, restore the whole db.


1

VisualUIAVerify relies on the MSAA interfaces to find the information about all the controls on window UI. If the third party components used in your application doesn't support MSAA, no way that test frameworks that relies on MSAA to work. There are a few options: Check out the testability support with the third party component provider, they may have ...


1

To answer the question in the title, of course a developer can write their own tests, but the developer likely has some blinders and assumptions, and may not test all the edge cases, only the ones they've considered. The skillset between developers and testers overlaps, but isn't a perfect intersection. Joel Sposky wrote about some of this before. It ...


1

I would say you are partially right. Unit testing is a good practice for development and ensures your code does what it is supposed to do. That should probably be written by the developer and then executed on continuous integration. Code reviews should provide a good check to ensure that the code is correct as well as the unit test being correct. True QA ...


1

So when targeting Unit tests it's usually a pass/fail. When targeting a web application for UI tests there is a varying amount of results and not just a pass/fail at a test level. If using something like Selenium on a unit test framework I recommend 3 things that have great benefit if done properly. Develop your own result output where you can define ...


1

Our approach to the situation in short is to tolerate the situation that the build is not completely green. We track which parts of the software fail. If we consider the issue as a bug and plan to fix it in the future, having a red light in that feature is important information to us. We have categorized features in a requirement tree which status we ...


1

Manual Testing For the beginning it is very useful to know what kind of tests exists. So you can explore the ISTQB Glossary to discover them and testing terms in general. After that you could try to get involved in some open source projects. You could install and test them and contribute some bug tickets. Mozilla has a QA area. (Other companies / ...


1

1.In eclipse i have executed the tests they are working fine, how i have to execute them in production server? Your tests can run in every environment. You can have a Selenium Hub and many VMs with different operating systems and browsers. But for the beginning the tests can also run from your local computer. You can choose against what environment ...


1

@logician: Please go through this link seleniumhq here you will get all the information. And to automate take any web application.


1

In my experience, the answer is both yes, and no. Obviously a developer can write automated tests for a feature he/she implemented. Whether that developer should write those tests is another argument and depends on - among other things - the type of automated test being written, the style of development, whose time is better utilized performing which task, ...


1

The activity that a developer should not do against their own code is really test design, not test execution or test automation. If the developer is doing their own test design, anything the developer forgot to think of won't be tested, by definition; a separate tester can think of things the developer did not. If the developer is automating a test case ...


1

Depends on structure and skills of your development team and testing team. If your testing team has only manual/exploratory testers with no skills/time/resources/etc to write automated tests, and you want automated test, the only people who can write them are developers, and then it is much more productive if developers writes tests for the new feature s/he ...


1

The highest quality product with the fewest production defects I ever worked on had no QA team. The developers were responsible for end-to-end service and the quality expectations were clear. The problems arise when changes are rushed through without sufficient validation - whether that is by QA or Dev. Developers are often best placed to automate tests and ...


1

Remember that the ultimate goal is to create high quality code. Anything you do that gets you closer to that goal is OK. So, yes, it's OK for a developer to write automated acceptance tests if they want. The more important question to be asking is, is it OK for the developer to be the only person to write automated tests for the feature they are working on? ...


1

Overview Robot framework is an excellent choice that meets all of your goals. Robot can be used for UI tests (via selenium), REST and SOAP service tests, database tests, and just about any other type of acceptance test. You can even use robot tests to improve your manual testing process. Robot is keyword driven Robot is keyword-driven, which makes it very ...



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