Understanding Logs as Part of Your Expected Results

Logs in Software Testing

1 / 1

How would you use logs during Software testing?

Bug reporting

Exceptions and Errors

Your score is

The average score is 100%

0%

Restart quiz

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.

The question is – What is happening behind the scenes?

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

Pretty much like magic.

The truth is, magic never happens. It’s just the sleight of hand, diversion, and so many other things that we never seem to notice.

Pic Courtesy pexels.com Nikolay Ivanov

The same trick can be applied to Software testing. The expected results should contain the standard apis. It should also include any ‘stuff’ that should  be running in the background 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. Especially the low priority ones.

Manually, for High priority cases to start off with.

Let us know what your thoughts are in the comments section below.