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.