Category Archives: issues from the void

Outlook broke important business feature

Reading Time: 1 minute

TL;DR

This post is about Outlook broken business feature, carbon copy recipients.

In e-mail, the abbreviation CC indicates those who are to receive a copy of a message addressed primarily to another (CC is the abbreviation of carbon copy). The list of recipients in copy is visible to all other recipients of the message. In common usage, the To field recipients are the primary audience of the message, CC field recipients are others to whom the author wishes to send the message publicly, and BCC field recipients are the others to whom the message is sent.[source]

Carbon copy feature in email is de facto a standard business rule. If you are implementing email client, you should implement cc feature in that way.

And here is Microsoft 2016 cc feature:

issues_from_te_void_2 issues_from_te_void

And here is received email:

issues_from_te_void_2

You can not distinguish to: recipients from cc: recipients.

Business impact.

I received such an email, and replied to project manager to explain who is responsible for subject of his email. He replied (not very pleasantly, but that is the different issue) with highlighted to:  in message conversation automatically attached in message reply, and that I should know the cc: rule. So in message reply, you can distinguish between to: and cc: fields. But not in original mail.

Can I move to other email client? Answer is no, because Outlook is mandatory tool in clients organization and I am obligated to use it.

Update after Facebook feedback (Thanks Vanja and Igor!)

This issue is not consistent with Outlook history, because in previous Outlook versions that worked. Also, Gmail is not adequate alternative email client for this feature, because gmail also does not show cc field.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Android back arrow icon UX issue

Reading Time: 1 minute

In this post I will present a UX issue from a very famous engineer cultured company.

Every user interface should be developed in such manner that it is self descriptive. It should be self documented, so menu items or input fields should have labels that clearly describe their purpose. Tooltips must not be some fancy technology, but they should contains small pieces of business logic that describe how is this part of form connected with business logic.

Icons should also have that purpose. If I want to save something, please put floppy disk icon (thank you Microsoft for that mnemonic).

And then we have Android back icon. What is first mental image in your head when you see that icon? What is the purpose of that icon?

For me: I will first go right in menu, and when I get there, Android will AUTOMATICALLY make a U turn and then I will go to the left in application menu.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Feature analysis for my Internet banking application

Reading Time: 2 minutes

TL;DR

This post is feature analysis of my Internet banking application. As a user, I am not satisfied how those features are implemented because using them I spent much more time than expected.

As a user, I want to pay my bills reliably and as fast as possible. Feature that I used every month is to ADD MY BILL TRANSACTION TO BATCH OF TEN, and then I confirm that transaction with ONE transaction token.

SELECT PAYMENT TEMPLATES is also very important feature, because using them I only have to change one dynamic part of every bill, that is my PAYMENT ID created by the owner of the bill.

Combining those those two features, I spent less that 20 minutes to pay all my monthly bills. And that is acceptable for me.

Current system is live from the beginning of this year, which means that I used feature, CREATE A PAYMENT TEMPLATE, in the old system. All payment templates were successfully migrated to the new system.

This month, I needed to update one of those templates, and all the frustration and fun began. In user interface, there was no obvious information how to do that (obvious information in user interface is my prefered way of application documentation). Then I checked official user documentation.

Search for predlozak, croatian word for template. Second word will reveal Slika (picture) 10.17 and observe upper right corner. Yes, this is where you select to save NEW TEMPLATE.

So, there is no feature, UPDATE TEMPLATE. You need to delete current template and then create new one.

And here comes the BIG BANG FEATURE! In picture 10.17 you can see how to pay a transaction. Wait a minute, what does this have to do with creating the template? Well, they decide to merge two features, pay ONE transaction and during that feature, mark that you want also to create NEW TEMPLATE from that payment transaction. Simple and logical, if you are a Vogon.

So, here was my workflow:

  1. Add payment transaction to transaction batch of ten.
  2. Remove it from batch because I wanted to update it.
  3. Delete current template.
  4. Create new payment, mark that I want also new template from it
  5. Pay just one transaction
  6. Continue with adding other transactions, using their templates that need not to be updated, to batch transaction

There is also one feature, that I call ANNOYING FEATURE. Remember that in every PAYMENT, I need to update PAYMENT ID, hard coded by the owner of the bill. Croatia Vogons created a set of rules for that PAYMENT ID (and increased croatian employment number for 5000 thousand).

And bank developers decided to implement MAGNIFICENT FEATURE, check that business PAYMENT ID WHILE I am typing it in input field. Yeah for Javascript! Problem is that they trigger rule check BEFORE I FINISHED typing!

How is your Internet banking application these days?

 

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

InMusic festival UX issue

Reading Time: 1 minute

TL;DR

Next week is InMusic festival in Zagreb, on beautiful Jarun lake. I checked schedule for Skunk Anansie and found one user experience issue.

 

Observe the post feature image. That is schedule for day when Skunk Anansie is playing. Can you tell me which date is date?

No, because selected day is not marked differently from other two festival days!

I hope that I will guess the day when Skunk Anansie is performing.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Tester and UEFA Euro 2016 competition

Reading Time: 1 minute

TL;DR

One example with an issue in context of Uefa.com site.

Yesterday was kick off day for Uefa 2016 Championship. Great time for football fans but also some opportunities for software testers.

This morning I checked uefa official site and clicked on today’s featured video. Here is the page:

Screen Shot 2016-06-11 at 12.40.37 PM

Feature is broken on latest Chrome and Firefox.

Using Chrome developer I found out:

  • that site is using Javascript
  • as issue is active for 12 hours, UEFA is putting all their horses on TV rights income
  • on uefa.com there is no info how report an issue. I will use twitter hashtag #euro2016.

Go Croatia!

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

g+ share ui lockdown

Reading Time: 1 minute
TL;DR

In this post I will present g+ share issue that I experience when I tried to share one of my blog post from the blogger tool. This post is inspired by genuine Ben Simo blog Is there a problem here?

Video speaks for itself.

What is important here is to note that this video is not enough for issue report. Why? Because developer can only see the issue manifestation. This video could only entertain the audience. But it does not contain information to replicate the issue.

BBST RIMGEA gives what are the ingredients of excellent bug report.

For example, R stand for replicate. I have not replicated the issue from the video. I did not do any analysis during the issue (for example using Chrome development tools). And using that video, developer can not replicate the issue.

Dear tester, if you only submit manifestation of the issue in your bug report, you are not good tester.

What can you do? Take the Bug Advocacy course:

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather