164 reputation
11
bio website leonstafford.com
location Masterton, New Zealand
age 32
visits member for 2 years
seen Oct 16 at 21:29

Perpetual Python learner and dabbler in Linux.

Specific interests are:

  • automation
  • low-resource computing
  • unicorns

echo "7364's853648s318s12" | sed -n 'y/12345678/edhtwaT /;p'


Dec
24
comment Should web pages be tested for ZOOM levels?
Hi @JoeStrazzere, agreed in the context of Google Maps. For our specific site (think Job site, with lots of text info) we can definitely see zoom in cases, especially for iOS users (25% of our userbase). With iOS Safari, it does not allow zooming out passed the baseline zoom level AFAIK, so I'm basing assumption on that. Still, I think based on the feedback here and thinking about it more, in this isolated case, we will fix the bug. Going forward, we will test zoom IN levels for majority of information heavy pages and possibly OUT for specific contexts.
Dec
24
comment Should web pages be tested for ZOOM levels?
Thanks @Bj. Primary customer profiles exist, but without a set of personas. I think I can assume for now that zooming IN will be prevalent, but OUT very rare.
Dec
24
comment Should web pages be tested for ZOOM levels?
Thanks again @JoeStrazzere, at this point, it's an educated guess based on the content on the site which does not people to zoom out (I would assume the same for say Wikipedia). Your point of what would I say to the customer is a good one, though and helps with perspective. Some more real user testing needed and if anyone mentioned zoom, I would assume more people would and even one potential customer's UX is worth the small time required to fix the issue.
Dec
23
comment Should web pages be tested for ZOOM levels?
Thanks @Usman. As a Product Manager, I'm conflicted with feeling that the product should of course aim for bug-free status, at the same time I don't necessarily have infinite resources, so need to prioritize for the use case of the assumed 99.9% of users vs the .1% who are zooming out and encountering layout issues. I think the bug found should be filed and I would not discourage AdHoc testers from reporting similar issues, but will not include it as part of any recurring test plans.
Dec
23
comment Should web pages be tested for ZOOM levels?
Hi @dzieciou, as mentioned in my question, should be a very rare instance that people would do this for our website (zoom out), zooming in may be a lot more common especially for iPad/iPhone users, though this does not affect our layout as zooming out currently does.
Dec
23
comment Should web pages be tested for ZOOM levels?
Thanks @testerab. I can understand that similar to choosing which browsers to test being determined by what our audience uses.
Dec
22
comment Which automated tests do devs create vs SQA staff?
Thanks @Phil, yes, I think as others have mentioned, there are different tests which may be suited to different staff roles but the key will be in collaboration.
Dec
22
comment Which automated tests do devs create vs SQA staff?
Thanks @user246, I think that is also a very good perspective to look at this from.
Dec
22
comment Which automated tests do devs create vs SQA staff?
I think as another poster mentioned, the roles may be interchangeable, but with our current resources and to entice developers to write better code, it makes sense for devs to be the ones to create white box unit tests. SQA staff will create front-end/input based tests.
Dec
22
comment Which automated tests do devs create vs SQA staff?
Thanks @RumVerse. I think the difference between white box and black box helped me understand the differences. So, developers know and are required to know the code they right, making it "white box". SQA staff may not need to know the code inside out to create functional black box tests.
Dec
22
comment Which automated tests do devs create vs SQA staff?
Sorry, AdHoc by testers identified 600 bugs.
Dec
22
comment Which automated tests do devs create vs SQA staff?
Thanks guys, @Usman is actually one of our new remote SQAs. The word there is "functional tests"... vs "unit tests". What is the difference, with an example if possible?
Dec
17
comment What kind of documentation do I need for testing new site against old?
Thanks @SheyMouse, unfortunately, there was never any SQA done on the old site by engineers, but seeking input from the Customer Service Manager should highlight what the former first line of defense dealt with most.
Dec
16
comment What kind of documentation do I need for testing new site against old?
above comment may have sounded a bit dictatorial, but I will be devloping this first module's documentation with collaboration from stakeholders (product owner, marketing manager, customer service manager) and then will consult with experienced but new to our company SQA Engineers :)
Dec
16
comment What kind of documentation do I need for testing new site against old?
Thanks @Joe good advice. I went with this product requirements document as an outline to be used per site module and have started on the most pressing one myself, realizing that it's not really something anyone else has the product knowledge and oversight to really do to my standards. I am realizing how important this is and investing into it so that SQAs, technical marketing team, etc can really use it to know how to do their part of the job. Anything which is included should not be missed & stakeholders will buy-in.