Tag Info

New answers tagged

0

For more understanding review this blog. http://software-testing-tutorials-automation.blogspot.in/2014/09/how-to-drag-and-drop-element-in.html


0

I would definitely recommend broadening the types of testing you are doing, as well as seeking out more complex functionality to test. Have you ever done performance testing? Reliability testing? Security testing? Database testing? What about designing scripts that actually crawl the functionality of your website without you telling them what to do, and ...


2

"Test automation" means more than just automating user interfaces that run in a web browser. Someone with good programming skills should be able to find many other ways to use software to test software. Here are are couple of examples: Write API-level integration tests. If developers test, they probably focus on unit tests. There is a middle ground ...


0

I don't know if this is what you are looking for but as is case for a lot of people we don't have a choice of what to automate. So what I personally try to do is also figure out what can I do that would prove useful for the software but still be exciting. One of the things is performance testing. I haven't seen too much that automated tests also maintain a ...


0

Check out some interesting challenges on https://challengers.flood.io/


1

A CMS can be challenging. You have content moving, user permissions, generated IDs, etc. Try out WordPress. I snapped out of the automation boredom once I hired someone to take it over and I took on security testing and process improvement. Start with OWASP for security.


1

I think Single Page Applications type which last time gains more and more popularity can be hard to automate, because this type of pages are dynamically loaded. Every action on page can load new div from server without reloading whole page, just for example simple paste table to div. Webdriver cache webelements on page load, and dynamical loading of html ...


3

We have had a very hard time automating the Google Maps API. Test case: Surf to Google maps: https://www.google.nl/maps Find an area with known location Click the known location (without the use of mouse-coordinates, should also work when zooming, etc...) Verify the location box with details opens Retrieve the phone number This is very hard, because ...


0

I think the issue here because your has style="display: none;". In this case, I think you should click on the div first and try it on Select. Below is my code: WebElement divClick = driver.findElement("//div[@class='form_row']/div"); divClick.click(); WebElement dropdown = driver.findElement("//select[@id='dn']"); Select select = new Select(dropdown); ...


0

I'd go with a database or file system equivalent (such as CSV) for a number of reasons: SQL querying is a lot easier to learn, use, and maintain than regex Updating your baselines for changes is a matter of a simple update statement or file copy You can control what appears in your baselines and output if you pipe all your output to file/database (or if ...


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 ...


0

Some pitfalls I encountered by using simple database operations. Some might be applicable for API and SQL. What is the best order to enter data? E.g. I need to enter customer. So I fill a table of zip codes first. What kind of data is available? E.g. I need a valid zip code. Only a third of the table is loaded. Ofcourse mine is not in the table, so I ...


0

Microsoft Test Manager (MTM) supports attachments and it is integrated with Team Foundation Server (TFS). While you executing the test cases you can add screenshots or files to the failed steps.


0

First, as @Steve Barnes says, you should NEVER run test on production database. If you do, you are asking for problems, and you WILL get them. Second, part of your test should be test of creating user: if you create user via SQL script and not your app functionality, you are not testing that, and you are creating special program which needs to be ...


0

If you have RW access to the source: Build your own APIs/Test Harness into a test solution referencing the source code. This will give you a massive amount of benefits including familiarity with the code, additional unit/integration test coverage and ensuring that you're test set up is executing exactly the way that a user's data would be set up. This will ...


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 ...


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 ...


0

Here is my recommendation in order of preference: API SQL (Avoid and may be used as a stop-gap-measure until API is available) Create user script (takes time and may have false positives) Most applications these days have such APIs and if your application doesn't have these these it may be worth considering in upcoming sprint/releases. In case you need ...



Top 50 recent answers are included