Hot answers tagged

5

Absolutely you need negative cases! In fact developers will likely have focused on the positive cases so the negative cases not present can add the most value! I recommend the following breakdown: Happy, positive tests. These test what happens when the user does everything right. They also used defaults as much as possible for input values Sad, negative ...


3

One possible way is to force a change in a parallel session or in the database with a script. Then you can keep polling for some seconds until the new data becomes visible. I would expect the feature is not to refresh the page, but to refresh to show new data. Test the feature, not only the known behavior, thus test why the page refreshes instead. Ask ...


3

how many test cases can we write? Every time you ask that question, the answer will be "it depends". There is no industry standard or best practice that says, "You need 9 test cases" or "You need 1.4 times as many negative tests as positive tests." If your business contract includes conditions around test cases, you should probably honor your contract. ...


2

If you write this same question on Google You will get a long list of tools, applications and browser addons for running a spelling and grammar check and a link test for websites. Personal what I do is copy the content of web page and paste it in a Word Processor like MS Word or Libre Office Word and run the spelling and grammar check in it for find the ...


2

Separate your actions on a webpage from test cases. Follow Page object pattern/framework. You can use junit or testNg unit testing framework to write your test cases. I would advise you to use testNg as gives you lot of flexibility. Now you like to validate all 8 steps that you want to execute, now the question is what if first step fails, what do you want ...


2

You can write test cases for both positive and negative scenarios. For example; phone number starts with a 0 phone number does Not contain "+" What most people tend to do is to devise their negative tests to be a positive scenario. This way, each test that passes is in a True state. This makes it far easier to interpret the results of your runs. The ...


2

You can download a 90-day trail of Visual Studio 2015 enterprise to test it out. The Coded UI testing framework relies on the Microsoft UI Automation framework. Any GUI tool that does not implement MS UI Automation hooks cannot be automated with Coded UI. It seems the Java SWT uses native windows controls and this should be automatable with Coded UI ...


2

Personally I wouldn't go with the xpath but instead create a list of the WebElements via driver.getElements(By.tagName("li")) but if you're hellbend on using xpaths you could use a simple try catch structure to see if the current element exists and let it return the last existing path. I'd try something along the lines of static String getLastElement(){ ...


2

Yes. You can create an application to run your test scripts, when you create your test projects they are just libraries/dlls that you have created and they do work just like any other library/dll. add to references and you should be able to call specific tests and get their pass/fail value when they are finished.


1

Maybe your xpath is wrong. You can use add-on FirePath for Firefox to get the xpath of the image. In order to let the link be clicked, your xpath should end with tag a, not img. For example, suppose xpath of the image is ".//*[@id='navbar_notice_6']/p/a/img", you should remove "/img", then your command in java will be driver.findElement(By.xpath(".//*[@id='...


1

Think about the three steps for every test setup execute teardown Ideally this is done for every test and the database strategy used between tests is truncation. Frequently this is deemed not possible and seed data is used which would slow down the tests too much if deleted each time. In those cases each test should use the database strategy of rolling ...


1

The best reference to design your test cases is API documentation a.k.a API contract. This document describes: How to call the APIs What to expect from them Generally, you can have these kind of test levels for your APIs (based on the contract): Acceptance testing Contract testing e.g. pack (includes your idea: schema validation) Performance testing


1

Ask development to place a HTML comment that has the timestamp, e.g. <!-- 06-jan-2016 08:09--> or add it to the actual page so that tools that have access to the full dom can easily access it, but make it not display on the browser <div display:none">06-jan-2016 08:09</div> If it has to be present but not visible then <div ...


1

Prior to automating a test case/test pack the checkpoints must be agreed. If you are purely automating a functional test case which does not validate how long it takes between one step and the next, in that case as long as the agreed journey is automated and functional checkpoints are met, the test case/pack is considered to be completed from scripting ...


1

Automated testing is done when all the current functionality is covered by the tests, i.e. test case coverage. When the automated testing is done I always recommend manual testing on top of this. If you have specific performance and/or load tests they will have criteria as to whether they are passing or failing, i.e. completing within the time specified.


1

I haven't found a solution, rather an alternative. I have used Jenkins and used to BuildFLow plugin to create a Build Flow job. I use this job to call 3 other jobs to run parallel. The 3 other jobs are Maven jobs which are each pointing to their own test XML files which contains the tests classes I need to be run parallel. It greatly reduced the time of ...


1

I would suggest you not to bind any particular automation tools to your testing. Which means that at the test framework level, you need to have a shared layer as the interface to the test automation developers. While underline framework development could use any automation tool which works fine with different kinds of applications like web and win form. In ...


1

If your application doesn't provide an interface for object based UI automation (such as MS UIA), which seems that's the case for you, and if you can't follow Andy's very correct suggestion; then you should look for an image processing based tool. Sikuli is the first that comes to mind, being open source and very successful (and probably being used by some ...


1

To become an automation QA Engineer is a process and you are right nowadays it is really difficult to find a job only with manual skills. My suggestions is to start with grey box testing first. Watch what there is behind a web page,a single page application and mobile apps. You definitely should start with some proxy tools. To learn to manage your ...


1

Form above explanation it seems that failed-testng.xml gets deleted when you re-run your tests in Post task under Jenkins, because when you run "mvn clean" it will delete the target folder where failed-testng.xml was present. To verify this you need to access the Jenkins workspace, but your software testing company might not have the access to it. Further ...



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