OS X Calendar application usability issue

Reading Time: 1 minute

TLDR

Every application has state. In this short post I will explain how application state causes usability issue.

One of the greatest challenge of every tester is to manage its time. In order to manage time, we use calendar. Either old style wall calendar that can be flipped in order to browse it, or cloud based application such as Google Calendar. Sometimes I use OS X Calendar application. And I am not satisfied with its features.

In BBST foundation, in chapter on Oracle’s, I learned that tester could create model of application under test. Application state is important building block of such model. I noticed that OS X Calendar application has states which downgrades its usability. When I browse through the calendar (e.g. I want to see next month) and the I exit Calendar application in that month, when I open again application, it shows that month, instead of current date. This feature was the reason of many mistakes that I made related to date input. For example, once I created invoice with wrong date which caused a lot of headache to my bookkeeper.

This is issue because (HICCUPPS):

It is inconsistent with comparable product. Google Calendar does not have that feature.
It is inconsistent with user desires.
It is inconsistent with purpose. Calendar should always show current date.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Report on Webinar Driving While Driven: The Way of the Skilled Tester

Reading Time: 2 minutes

TLDR

Yesterday I participated in webinar Driving While Driven: The Way of the Skilled Tester. Webinar moderator was Keith Klain, CEO of Doran Jones and Executive Vice President of Association of Software testing. Webinar author is James Bach, Creator of Rapid Software Testing . In this post I will write about webinar technical experience and my takeaways and a-ha moments.

We all have got opportunity to participate in some webinar. Some of those webinars offer great free educational content, but we fail to participate from various reasons.  As Driving While Drive schedule suited me (Friday 8 PM), and I would get a chance to listen Keith and James in live session, I committed to participate in this webinar.

Technical setup was easy, by clicking on webinar link I was redirected to download GoToMeeting software, and I was ready in less than a minute.

Keith started with introduction and then James took the floor. Quality of audio was very good. We could ask questions in chat box which would be answered in the end of webinar. Listening to James was real pleasure. Excellent tester must have excellent speaking skills. My mind did not drifted away for a second, because every sentence is a brain teaser. Also important note, while James was speaking, Keith interrupted him with follow up questions. James easily passed speaking floor to Keith, and easily continued where he was interrupted.

This is very important skill when you need to deliver information to engaged audience. In my practice, other speaker usually gets mad when I interrupt them with follow up questions.

James provided four documents:

1. Build analyst
2. Exploratory testing dynamics
3. Rapid software testing vs factory school
4. Testing and checking

This webinar goal is to explain what is School of context driven testing. James is one of the authors of that school.

Here are my notes:

follow process – not, you are creating it
procedures – yes
common sense – knowledge everybody knows
cdt – question what people think is true
cdt is not common sense – against education system (sit down and shut up)
fast food – growing potato – can advise you but can not do it for you
child steering straight the road – is he driving, yes at that particular time and situation, empty road
why practices work at some time, do I need to change them – CDT
I am context aware – not cdt
I am not cdt – only one way to do something
context imperial – insertion, a little bit is ok
when I want to work only with system thinkers
cdt – respect context and problem solution
universe claims that this is best practice, for me this is best practice
Am I cdt: do you work hard to create your skills?
compare cdt with others on problem example
other: concrete procedure in document, spec, contract
cdt: what is patent? Test all definitions. Decision by judge based on those test reports.
formalization – limitation
create procedure – my question
father (client) yell at me
is there something that does not have value for anybody? (system thinker question)

cdt heuristics or how to become cdt tester:

1. learn how to design experiments

At that point webinar lost audio. There will be scheduled another session to finish qa with James.

My 5 cents:

Can we apply context driven on other crafts, e.g. cooking?

If CDT also creates procedures, what we should do with those procedures when we are done with the project?

Conclusion

I recommend you this webinar.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Testival 2015, a software testing event

Reading Time: 1 minute

Registrations for Testival 2015 are open! Formerly know as ViaQa, this year this software testing event will be hosted in Microsoft Innovation Center in Split, Croatia. This event is combination of unconference format and speakers. We have two confirmed speakers: Maaret Pyhäjärvi and dr.sc. Dario Hrupec that will have opening and closing notes. In between, sessions will be chosen in unconference manner, by you, participants of the conference.

Event is scheduled for September 18. and 19. 2015.

If you still have doubts to attend or not, just a kindly reminder that Split is one of filming locations of popular HBO show, Game of Thrones!

See you in beautiful Split!

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Report on ZagrebSTC #21

Reading Time: 1 minute
Julian, Oradian COO, presents Oradian

TLDR

On last Thursday we met at Oradian who hosted the meet up. Julian presented Oradian, their way of working, business case, and got opportunity to meet testers from Zagreb area. Nine people were present.

We started with Oradian 10 minute presentation. Their business are microfinancing services which they offer in cloud for underdevelopment countries. Their are in position to drive clients business process because in those countries this is in early phase.

Their software develops in 4 weeks sprints and key word is constant change! Team consist of devops, developers and QA team.

After official part, we continued with our usual introduction of every tester and what interesting issue they have found in previous week. And then magic happened. Those introductions generated very interesting discussion: load testing, QA team in 4 week sprints, regression testing, selenium, cloud system monitoring, finding the root cause of “slow” transaction, vim. Two and half hours of lively discussions. I am very satisfied with this meetup. My takeaway are vim tips and tricks that I have not been aware off.

Important thing is that Oradian is hiring, here is their job listing. Job description is just orientational. If you think that you are up for some of the positions, feel free to contact Julian over linkedin and mentioning that you heard about job listing over Zagreb STC.

  

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Selenium RemoteWebDriver over http

Reading Time: 1 minute

TLDR

In this post I will explain how I connected knowledge from two testing domains, security and UI automation, in order to achieve proper UI automation stack configuration.

 In order to be able to use various browser/os combinations for ui automation, I am using SauceLabs, cloud based testing provider for web and mobile. SauceLabs is running Selenium Server instances to which you are connecting using RemoteWebDriver.

Here is how to do that in Ruby:

What bothered me is that UI test would open http connection and testing infrastructure would be vulnerable to man in the middle attack. By investigating the Selenium documentation, it is not possible to run Selenium Server with https.

What is next? SauceLabs has its own product, Sauce Connect.

“Sauce Connect is a secure tunneling app which allows you to execute tests securely when testing behind firewalls via a secure connection between Sauce Labs’ client cloud and your environment.”

That means you are still using http towards Selenium sever, but over secure tunnel.

“Data transmitted by Sauce Connect is encrypted through industry-standard TLS, using the AES-256 cipher.”

What is interesting is SauceLabs official statement:

“You should use Sauce Connect whenever you’re testing an app behind a firewall. Sauce Connect is not required to execute scripts on Sauce.”

This should be paraphrased:

You should use Sauce Connect when your testing scripts are using sensitive corporate data.

Never put aside your testing domain knowledge, you should always combine them, especially when clients security is at stake.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather