I'm on my final semester on my BSc in Information Systems. As a part of this semester, me and two colleges are working on a project with a large company providing services mostly based on the SharePoint platform.
Our task is to revise their testing process, with focus on testing the responsive design of their SharePoint solutions, i.e. solutions run in browsers on different OS and different devices with different screen sizes.
My questions is therefore regarding design testing. I've been reading up on the general software testing process, from test case design to script writing. I can not seem to understand how (responsive) design testing is different from the "general" software testing process, if any?
Furthermore, I've been looking at numerous products that might aid the responsive design test process. This product in particular caught my eye:
From a professional point of view, would this product be viable for responsive design testing in a large company environment? Is there a more viable option? I know this question is vague, but I am simply looking for a professional opinion on this, since I have no professional experience with software testing.
Lastly, as @milinpatel17 stated in his answer to this question
No matter which emulator or tool you use, it will never give you proper result as the original device. The reason behind this being the difference in the environment. The environment, that is, the hardware and software that a PC operates on is different than the one's of a phone. Hence, the browsers are also different and they render webpages and their content in a different way. The emulators running on your computer will try to give you as close results to a phone as possible but never the actual result as you will get on phones. So sometimes all the emulators will do is change the screen resolution but it will not render the script as a mobile browser would.
I understand that the best way to test your products and solutions is on actual devices. Is this actually applied in practice? Are emulated environments the second best solution?
To sum up my questions
- How is (responsive) design testing different from the "general" software testing process, if any?
- Would BrowserStack be viable for responsive design testing in a large company environment? Is there a more viable option?
- Are companies testing their solution on every possible handheld device, tablet etc. in practice? Are emulated environments the second best solution?