Solution :
Please try setting "1" in the "Device Pixel Ratio" column for the virtual browser you're using:
https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/properties/open-apps/web-testing/virtual-browsers.html
ApplePen :
Hi,
> Sometimes elements probably doesn't appear in the page when the browser is not in maximum size.
Agree. But at the same time, I've seen a lot of cases when page that looks good in maximized browser (read - in a big enough viewport) becomes visually corrupted on a smaller viewports.
And also, if something is not visible on the page in a smaller viewport and I don't have any hint that this something must be present, how I as a user can get an idea that this something must exist and can be used? Personally I consider such page design to be a bad user experience.
And, finally, personally I used to use windowed but not maximized browsers. (And been a test engineer, I am always happy to see corrupted page layout in a windowed browser. 🙂 )
AlexKaras Your opinion that inspired me. Thanks a lot.
We definitely need to stand as a user to test.
Sometimes, we make automation test cases and ignore that.
I will pay more attention for it later.
About the browser size:
Do you have any suggest how to design it in test?
Ex. Do we test all cases in normal size and retest them in another size?
ApplePen :
Hi,
> About the browser size:
For example, you may consider the approach like this:
-- Talk with your UI designers or just explore the tested application to find out whether it uses different layouts for different viewport sizes and, if yes, what are sizes (breakpoints) that trigger layout change. As an example: https://getbootstrap.com/docs/4.3/layout/grid/#grid-options;
-- Create test code that makes it possible to drive the tested application using all (or just required) layouts.
Then, you should be able to create a set of required tests according to your test plan.
For example, using the breakpoints from above, you may execute a cursory set of tests setting viewport size to 570, 576, 768, 992 and 1200 pixels and check that UI layout was set properly.
And then execute a full set of functional tests that verify functionality using most expected viewport sizes, for example, 770 and 1600 pixels.
AlexKaras and ApplePen, thanks a lot for this great discussion!
svishwakarma did you manage to make this work following the advice? Please let us know the solution!
Solution :
Please try setting "1" in the "Device Pixel Ratio" column for the virtual browser you're using:
https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/properties/open-apps/web-testing/virtual-browsers.html
