Hello! I'm Chamal Asela Perera.

I test code for living.

Persona Based Testing

People who involved in software quality assurance are increasingly being challenged to provide a better coverage of the tests. They are often asked to think like the end users, Be in customer’s shoe in order to deliver a high-quality product.

One of the best and interesting way to increase your product quality is to do persona based testing.

What is Persona? What is Persona based testing?

A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way.

Persona based testing is a software testing technique that puts software testers in front of customer’s mind and determines use cases/scenarios that customers will execute.

How to create personas?

There are many ways to create personas. The best way to think like the end users/or to be in the customer’s shoe is to get to know with your end users.

Below 03 questions can be asked in order to get to know with end user behavior.

  1. Customers of the product who use it as intended
  2. People who are not current customers but for who it is targeted and who will use it as intended
  3. People who are not current customers but for whom it is NOT targeted and who will NOT use it as intended

Let’s look into this by an example.

There is an application which serves the purpose of employee management. The application can be used to apply leaves/fill out appraisals and many more employee management activities. This application is also accessible to the entire company.

Let’s think of typical users who will use this kind of system.

  1. Management
  2. HR
  3. Employee

Now let’s drill down above user types further and add a few characteristics to them.

Management – Management won’t interact with the system often, But they will interact with the system to use specific functionalities. They probably use it in between meetings. Because of this management users are very impatient. They might use the quickest workflow to use complete actions. They use shortcuts, they want fast interactions.

To spice up things, Let’s add a name for our manager character, or else If you are super interested, let’s go for a theme – Superhero theme. I’m going to pick Nick Fury as my manager.

Characteristics of Nick Fury(Manager)

  • Won’t’ interact more often
  • Impatient users/Need faster responses
  • Using quickest workflow to complete action

Let’s look at some possible users for HR. Let’s assume they use the same workflow each time when they interact with the application,

  • They may focus on mostly used features
  • Complete each and every field possible
  • Be patient with slow responses

Seems good candidate for Black Widow(HR)

 

Likewise, we can go think many possible scenarios/many possible personas from different angles.

For the employee sections, Let’s think of an old user with a lesser knowledge in computers and always has trouble with the system.

That user probably;

  • Use the application really slow, takes the time to read each and every information available on the screen.
  • Using Internet Explorer 7.0 and no intentions to update it at all.
  • Maybe using zoom functionality of the browser to read out sections

Perfect candidate for Flash in Zootopia(Old employee)

 

 

 

Like this, you don’t need to maintain any limitations when creating personas.

Do not hesitate for someone like this……..

……….If your persona has characters such as;

  • Try to enter invalid data to input fields
  • Try to get error messages by doing various things
  • Going further beyond by entering SQL Injections or trying any methods to break the application.

In action

Once you are done with creating personas, then it’s time to be in end user’s shoe. Now, remember that you are no longer testing you usual test cases/test scenarios. You are executing your test cases/scenarios like Nick Fury the manager, Black Widow the HR, Flash the old employee.

You can arrange your test case/scenario document like this to make things more attractive;

TestScearoio_ChamalPerera.com

By using this kind of the way, it will not just make the whole testing interesting, it will also help to cover the real user behavior.

Note: This post was inspired from the Ministry of Testing, This is not afflicated with MOT

#HappyTesting

#FloodSL – How you can help

[Last Update 29/05/2017: 01:00 P.M]

Sri Lanka is currently facing the southwest monsoon and with the monsoon, like in the last year, there are flooding and displacement. As of now the number of deaths increases to 164 while 104 persons missing. Extreme weather forecasted to continue over next couple of hours/days as well, so the numbers may rise.

This year also there are some wonderful organizations/people get together for flood relief. Some techies also help them from what they can, Here is a consolidated list of the solution/options we have right now. I will update the list whenever I get more information

2017 Flood Crisis Map

https://www.google.com/maps/d/u/0/viewer?mid=1lMTSXqIUwgT8LCfeRdTqzDKob1Q&ll=6.470581407199456%2C80.58815789397192&z=9

This is done/maintained by Ganindu Nanayakkara. You can contact him & help him with updating the data.

Relief Support

http://reliefsupports.org 

 

This is a community-driven Open Source project to support relief support activities conducted by volunteers. This project was originally created to support flood relief activities in Sri Lanka in May 2017.

So If you are a developer, You can contribute to this project on GitHub

If you see any errors on the website or If you come across in any features which you like to include on the website, You can put them here

Disaster Management Centre

There are many ways you can help to DMC. Follow DMC_lk on Twitter for more details

PickMe Support

If you or someone you know is affected by the floods and needs urgent attention, you can seek PickMe’s help. All you need to do is open up the app, select the relevant location and click on the SOS icon. This will allow PickMe to receive your request and will be forwarded to the Disaster Management Center.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Credit Sharing from Mobile Networks

Dialog offers a free Rs.100 reload to those in the affected areas of Ratnapura, Kalutara, Galle, Matara, Hambantota, Dehiowita, Yatiyantota, Ruwanwella, Kolonnawa, Biyagama, Kelaniya, Kaduwela, Hanwella, Dompe and Padukka. Airtel is also offering free calls and SMS facilities to the people in the above-affected areas.

Mobitel has increased credit limit for postpaid connections by 50%, with prepaid connections getting free Rs.100 talk time and Rs.50 in credit limit(prepaid). Additionally, Hutch has provided free Rs.25 credit as well.

AirTel is extending free calls and SMS facilities for the people in the 5 flood affected districts to reach out for help

 

 

Online Donations: RedCross

http://www.redcross.lk/online-donations/ 

#FloodSL Tweet

All the latest tweets about flood situation can be found from the #FloodSL hashtag.


Featured Image Photo Credits: The Guardian – Credits to all the posts owners

Web Accessibility Standards – What, Why and How to Test?

Web Accessibility Initiative (WAI) is an initiative by World Wide Web Consortium (W3C). The main responsibility of the WAI is to work with the global software community to develop and publish guidelines on web accessibility. In 1999 WAI published the first version of the guideline, named Web Content Accessibility Guideline ( WCAG 1.0 ).

In 2008, WAI published the WCAG 2.0, which is the latest version of the guideline. WCAG 2.0 have been widely accepted as the definitive guidelines on how to create accessible websites

WCAG 2.0

WCAG 2.0 organized under 04 main principles and 12 guidelines. Each of these guidelines has testable criteria. It basically covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these.

We need something like this because an estimated of one billion people in the world have some kind of disability. 39 million people are blind in the world and around 246 million people around the world have low vision. More importantly, it is not only for those with disabilities. A fully accessible website is designed to be flexible and responsive to all people.

WCAG 2.0 principles and guidelines

  1. Website must be perceivable – Information and user interface components must be presentable to users in ways they can perceive
    • Guideline 1.1: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language
    • Guideline 1.2: Time-based media: Provide alternatives for time-based media.
    • Guideline 1.3: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
    • Guideline 1.4:  Make it easier for users to see and hear content including separating foreground from background.
  2. Website must be operable  – User interface components and navigation must be operable
    • Guideline 2.1: Make all functionality available from a keyboard.
    • Guideline 2.2: Provide users enough time to read and use the content.
    • Guideline 2.3: Do not design content in a way that is known to cause seizures
    • Guideline 2.4: Provide ways to help users navigate, find content, and determine where they are.
  3. Website must be understandable – Information and the operation of user interface must be understandable.
    • Guideline 3.1: Make text content readable and understandable.
    • Guideline 3.2: Make web pages appear and operate in predictable ways.
    • Guideline 3.3: Help users avoid and correct mistakes.
  4. Website must be robust – Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
    • Guideline 4.1 – Maximize compatibility with current and future user agents, including assistive technologies.
More details on the above guidelines can be found from official WCAG 2.0 – Documentation

Right, So what is for developers or testers? How to do the accessibility testing?

Let’s talk about the important part of the accessibility topic. How can you develop/ or test a WCAG-friendly website, or in another word – How can you ensure your site is not violating the WCAG 2.0 guidelines? Let’s look at a couple of tools which is available for the task.

NoCoffee

NoCoffee is an extension for Google Chrome, It acts as a visual emulator and helps you to understand how visually impaired users can view the web pages.

Chamal_Perera_Blog_NoCoffee_Image

Nocoffee visual emulator in action: [This is how retinopathy patient view your web page]

Google Accessibility tools

Another handy/straightforward Chrome extension from Google. The extension will add an Audit section ( Accessibility Audit ) in the elements tab to the Chrome Developer tool.  Audit result will appear as a list of rules which are violated by the respective page

Chama_Perera_Blog:ol Google Accessibility to

Google Accessibility Tool – In action

Google Accessibility Tool

Google Accessibility Tool – Results


aXE

axeDemo_Chamal_Perera_blog

aXe in action

aXe is again an extension for Google Chrome. It’s pretty easy to use and analyze your web application. You need to go to the Chrome developer tools section once you installed the extension and there you can initiate your session. One of the advantage in aXe is that you can navigate to the exact point in your source code where it violated the WCAG standard and fix it from right there.

Wave

Wave has been there for a quite a long period of time. Wave can be used to test any public URL and not like the other tools, it gives the result on a side panel, which is easy to analyze. Wave also has an extension for Google Chrome and Firefox.

Wave-Chamal Perera Blog

Wave in action

Developers can use these tools to make sure the site they develop doesn’t violate any WCAG rules. Testers can use these tools to find out the accessibility violations.

Advantages of following accessible guideline

Other than not involving in potential lawsuits, there are proven cases studies which indicated improving accessibility could increase sales. CNET received 30% off boost in their traffic after implementing a simple change in their videos. All they did was to add a transcript to their videos. More the people that have access to the website, more the reach.

Everyone should consider about the web accessibility, not because you had to follow the guidelines. Becuase it is the only way to ensure that disabled users have the same experience that other users have. Truth to be spoken, web accessibility is likely not something we’ve spend much time unless we had to. But now we have required tools/ ways to do, So let’s make the web accessible for everyone.

Microsoft Visual Studio emulator – Best in the business ?

Visual Studio emulator for Android is a great tool for debugging/deploy Android applications in the windows environment. For me personally, this is a much more convenient android emulator comparing with the Google’s own AVD emulators. Microsoft Visual Studio emulator for android uses the Hyper-V capabilities of the host computer, resulting in a faster launch. So it’s like, No more staring endlessly at the Android boot logo.

Requirements

  1. First thing, Your computer/development environment must meet the requirements to run Hyper-V
  2. 6GB or more of RAM

More details on the requirements is here

You can download the installer file from here

Features/Advantages

  • Apart from the speed, Microsoft Visual Studio emulator for Android supports a wide range of device profiles, Including devices from Samsung, Motorola, Sony, LG, and more.
Different device profiles

Different device profiles

  • You can install the APK files by using drag-and-drop method to the emulator screen. It also connects to the ADB, so development tools can target this.
  • Powerful simulations – You can try using the camera/map on the emulator
Additional tools available in the simulator

Additional tools available in the simulator

Problems you may face ( . . . or problems I’ve faced )

  • Unable to access the Wi-Fi or mobile data – Probably the most annoying ever I’ve encountered, Basically you can’t access any network/internet services from your emulator.

Solution ( . . . or the solution worked for me )

  1. Disable any virtual Ethernet adapters that aren’t being used.
  2. Go to Hyper-V manager & set the Emulator Internal Network Adapter’s Virtual switch to Windows Phone Emulator Internal Switch.
  3. Run the visual studio emulator on administrative mood.

Some more common problems occurred in the emulator can be found here.

Some more useful tips here

Ultimately this is by far the best simulator I’ve used for the mobile automation activities, especially after a couple of bad experiences with the native android simulators. So easily recommended!