Did you know? – Automated testing : adaptive/responsive
Here’s a first “Did you know?” on automated testing: adaptive/responsive website.
Getting quality assurance is time consuming and quality seems for some to be a grey topic.
If you look at the QA landscape these days it’s quite elaborate, many terms and techniques are used to achieve higher quality and lower the risk of issues:
- COMPATIBILITY TESTING
- CONFORMANCE TESTING
- FUNCTIONAL TESTING
- LOAD TESTING
- PERFORMANCE TESTING
- REGRESSION TESTING
- STRESS TESTING
- SYSTEM TESTING
- UNIT TESTING
- USER ACCEPTANCE TESTING
In the end the goal is to have a good feeling about releasing our software to the big outside world. That’s exactly what we’ll be doing upcoming weeks, and what we have done already for previous developments.
Manual testing is time consuming, performing the same tests over and over again, and can get boring to do repetitive work on a daily basis. A big time consuming test is “COMPATIBILITY TESTING”, where we want to know if our website works on all common used browsers like Firefox, Chrome, Edge, Explorer etc. These have different versions, and even worse, are used on different Operating systems (OS’s) like OSX, Windows, Linux, Android, iOS …. These again are run on different sized devices, iPad, iPhone, Nexus, HTC, Desktop etc.
The multiplier on these combinations can be huge, as in hundreds of combinations. For launch we have a goal, be responsive/adaptive on all major OS’s, devices and browsers.
This is what wikipedia thinks of it:
— “”Responsive web design (RWD) is an approach to web design aimed at allowing desktop webpages to be viewed in response to the size of the device one is viewing with.””
— “”An adaptive website is a website that builds a model of user activity and modifies the information and/or presentation of information to the user in order to better address the user’s needs.[“”
So yes, we have quite some combination to test, and that’s why we want to automate as much as possible. These days this role is more about scripting (dev), usage of smart tools and some good nerdy insights!
We use Browserstack.com to automate, simulate and emulate most supported OS’s, browsers and devices (so we don’t have to buy 400 combo-devices!). Running a test here is virtual for us, in the cloud as they say. We get the results back, and can see if a test is succesful or not. Based on that we can fix bugs and know for which version we have to fix it!
Here’s some video results on a test scenario: Searching an O’ring!
Zamro IT Crew