One more expected result to your test case

One of the most common test cases that we see is

Test Step: 

1. Launch the url of the app under test
2. Enter valid credentials in the login and password fields
3. Click Login

Expected result: User should be able to login

Alright, you just have one expected result.  Is that all there is to it?

The answer is a big NO.

As testers we need to have a 360 degree view.  One part of which is to look at the logs just for the login test written above

The expected results could contain the standard apis, and any ‘stuff’ that should  be running in the backgound for the login feature.

Unfortunately, most of us look at logs only when we see a bug.

Automation can definitely help for a lot of test cases.

Manually, for High priority cases to start off with.

 

 

Gamifying life of a software tester using AI/Machine learning

The life of some software testers simply seems to

1. Open their machine, look at instructions open a tool and

2. Start executing test cases (which are either written by them or by someone else) repeatedly

I have seen many testers simply having a routine, and executing the same tests – especially the ones that cannot be automated (sometimes several). This is so demotivating!

A pragmatic appraisal of several things can lead to a solution.

Gamifying testing – make testing habit forming.

How? While we may not have tons of content for a machine learning algorithm we do have some test cases as a dataset. However each test case can be subjected to tons of tiny variations, a simple change in settings, to change in a tester’s/user’s behavior towards the app. Each and every change in setting/different behavior can be used to make a recommendation to the tester to be tried out. A good natural language algorithm should do the trick.

Rewards: Tester can be rewarded for various reasons ranging from attempting to execute a recommended test just as it happens in many engaging, habit forming apps. Giving them some points, rewards, badges, certificates etc.

The situation should be something like, the tester opening the gaming app – the application recommends a test case with some variation/technique.

Hope it becomes habit forming. Can we make one such app? Are you game?

5G – Should we still write bug reports?

5G is a generation wherein a lot of text may become redundant and may be replaced by videos.  We are still in the process of writing steps to reproduce bugs, as a simple example, which can be replaced by simply recording a video.  The internet speeds are so high that uploading videos will become a breeze (size constraints could go down). We may have to rethink how some things are done fundamentally.  Any concerns regarding the storage of the videos may be done away with, as many ISPs are providing huge cloud storage as a bundle.  The days of automating the entire logging of information manually could slowly wane away as connectivity to different servers could be way faster. When I came up with my project Automated bug raiser   I did not anticipate such a big gamechanger like 5G that will transform our lives.  The above link will hopefully tell how bugs can be documented/logged.  This has many advantages:  It saves a lot of time for the manual testers and hopefully paves the way for better manual tests.  We may have to rethink how some things are done fundamentally.