Hot answers tagged

3

Spin up your own test environment and test against that. Let's face it, a public facing web page that's designed to attract DDOS testing isn't going to be a valid test candidate. The reason for this is that you'll not know how many other users are hitting a public server or the spec of the environment. If you ran 100 simultaneous users and the site went ...


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

Is there any other things I am missing from my list? You mentioned "Click on all "link" elements, making sure they are valid, e.g. there is no 404." Is that good enough? Shouldn't you check that the links actually go where they are intended to go? Are you checking for consistency on all the pages? Should they all have the same look & feel? Are you ...


1

Since you have asked about tests approach in general - think about the non functional tests that are needed for your project: Desktop / mobile and different mobile compatibility - how will the site will look like in them? performance - how quickly the pages will load? and how much will take to submit the form you mentioned and continue? User experience - is ...


1

The website itself should not matter much which technologies were used from the front end UI points of view, however there will be differences behind the scenes depending on languages and frameworks. I would make the following distinction in terms of a programming position: White box testing. This is testing the functions and code used to build the ...


1

To be precise and very specific there are no certain guidelines and benchmark defined for the web application related to their Performance. This is a thing which comes to mind of every QA, but unfortunately there are no worldwide or Organization wise accepted standards for the Response Time. It depends upon a number of factor including (but not limited to) ...


1

Obviously, you can't test everything. The question then is, how can you test as many of the most important things in the time you have available? This is a big question as written, and I'm only going to be able to cover it at a very high level. Apologies if I am not answering at the level you wanted, or if this answer is too basic :-) First of all, try and ...


1

I can recommend Ranorex. It works both with coding and without (just by capturing the actions). It also supports cross-browser web test automation (Chrome, Firefox, IE and Safari) as you can read here.


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

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


1

Could you please specific your kind of test? You want to do regression testing or ... If selenium web-driver is taken a long time, I think you should consider to : 1- iMacro: https://addons.mozilla.org/en-US/firefox/addon/imacros-for-firefox/?src=hp-dl-upandcoming 2- Sauce labs: https://saucelabs.com/ But before you get approach to automation, please ...



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