10

Apart from the fact your second piece of code will not even be compiled and also pretty much not representative since you're not showing us how exactly you would use the information of which particular iteration in the loop is currently going on, I would not recommend to use the loops in data-driven testing approach. Much better is to use well-know test-...


6

While this depends heavily on what part/functionality of a web app you want to test, there is a place and time for both. For example you might have a pop-up for informing the user about a cookie and have him accept (or decline) it. Typically this pop-up would only show for the first visit, making incognito mode ideal for repeatedly checking the pop-up ...


6

Generally speaking I consider it a bad practice if you are using different data combinations to run UI tests. I refer to this as data combinatorial testing. Generally speaking I look to be sure that the UI works. That a user can tab through the fields, can pick one value from a dropdown menu, can get to the submit submit button page, etc. I avoid ...


3

I would say you need to test app it in both modes if you're worried about caching issue. Most of the (functional) testing would be in incognito mode (you are testing how application works, not how it's caching data). The application must work for new users (it's even important than working for retention users) if you want to keep them coming back. Also ...


3

Usually, web application testing services follow the approach of covering both the browser modes during web app testing. Testing in Normal Browser Mode: This should be tested majorly for regular users in the app Cache/Cookies are locally stored on a user's machine, so validation is required, that the user does not encounter any issues due to caching ...


3

Back-end should be tested separately regardless of test results on the front-end. The main reason would be security. It's great that you have tested that front-end can send to back-end only numbers, but what if some person purposely use intercepting tool and forge request send to your back-end and change the number to any other naughty value? This may cause ...


2

It really has nothing to do with whether someone could alter the input file or not; it's a matter of what the code is documented/expected to do, and expected to deal with. You also need to know what level of testing you're doing. Are you testing the individual pieces (unit/function testing), or testing the end-to-end functionality (integration testing)? ...


1

I never test manual in incognito mode, now that I am thinking about it I do not see a lot of value in it. Automated tests will run against a fresh profile anyways. Manual testing is more for exploring, not for regression-suites. Your examples are valid, but should be seperate test-cases where you explicitly test that situation. Other reads: https://...


1

I sadly have to break with the rest and recommend ranorex for actual record and playback. Selenium is fickle and needs a solid framework around it to produce solid tests. The selenium IDE can't provide that because it doesn't know the needs of your application. Of course ranorex doesn't either but it's much more robust out of the box (which in my opinion ...


1

Selenium IDE for web (open source) and testcomplete for commercial(paid version) Appium desktop for mobiles. You can tap and verify whether its working. Inspector for desktop Provided you are working on Selenium/Appium


1

Selenium IDE is best record and playback tool for web applications. The new Selenium IDE has many useful feature that makes the tool unique from all the other tools. Here is the blog which explains about the new features and it benefits. Kindly go through it.


1

To test web applications and record it you can use the most used Selenium IDE. It is very easy to learn and documentation is also very precise. You just need to download the extension and than it's all set. You can start a new project by providing base URL. Afterwards you can multiple test under that project. The Selenium IDE records user's actions and than ...


1

Adblocker prevents some website traffic from reaching you. Therefore, the behavior of the website you are testing may be different from if you were testing the website without adblocker. If you wanted to test something as a user who was seeing the website for the first time, you should test it in incognito/private browsing mode without any extensions.


1

If you're looping 5 times and the test fails, did it fail on the first occurrence? The last occurrence? Is it failing on all occurrences? I like to have one assertion executed per test method if at all possible. Sometimes it's not possible because two properties have to be asserted at the same time. Tests should use obviously good conditions, obviously bad ...


1

It Depends Testing in a loop is a best practice when you're testing for things that require a lot of repetitive testing to come up with a positive or negative result. There is no One Right Answer to Every Situation, but there is usually One Right Answer to a Specific Situation. Each scenario has to be examined on a case-by-case basis. Test Once When you'...


1

In the end it boils down to the personal preferences. Personally, I do not like loops in the test cases because of the following reasons: Loops make the test case more complex In most cases a loop can be replaced with a data driven test which is more readable Loops break assert-for-one-thing thumb rule. I don't mean a single assert statement. When a test ...


1

Is it necessary to consider inputs that the front end blocks when testing the back end? The short answer is YES. The reason the answer is yes is because it is trivial for anyone with a little knowledge to bypass the front-end validation and send invalid data to the back end. It can be done with the tools built in to every browser, not to mention any proxy ...


1

If you're responsible for testing the entire solution then you have to consider all the components which compose that solution. If you are responsible for only back-end testing then you should concentrate on the back-end and do not care of any integrational aspects. In the latter case just leave that headache to the people who are put in charge of ...


1

Adding the DLL the plugin is compiled in (In my case the same project as the WebTest) to the TestSettings deployment will solve the issue and the WebTest will be able to use the custom plugin.


1

The link from Yu Zhang in the comments has some good things in it. It depends on the goal here, usually caching is for performance improvement. If that is the goal then I would think performance testing to be more appropriate than cache testing. If there is a unique situation involving specific cached values then you can utilize anything to read the ...


1

Some webpages display elements based on viewport size of the browser. I have used CheckMyLinks XPI with chromedriver in a test Automation suite in the past and it provided consistent results. Please ensure you use same viewport size and check for consistency of results or follow the below approach to verify if viewport size impacts number of links on the ...


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