Lessons learned (the hard way)

What we speak is what we have learnt. There are some very basic simple rules which we can follow as we grow as a Quality Analyst. In this post I will share a little of my experience.

Don’t try to test everything, or even close to everything.

You really have to factor in a lot of time for test case maintenance, even if your tests are well-written. Even it looks small, never under estimate, take time and think of scenarios which are hidden beneath. Some cases could be unrelated some can be deferred but yes think and over think, both in constructive and destructive way.

Don't try to test everything, or even close to everything.

Keep tests as small as possible

Test one thing at a time. On the same note, do not try to iterate over all data, unless you are trying to ascertain which cases to cover. It will just cost you test-execution time,
and again test case maintenance. Eventually, you will either cut down the test iterations, or you will give up and rewrite it.

Keep tests as small as possible
Businessman with hands behind head, sitting next to stack of documents on desk

Separate your positive and negative tests

Reading long-winded if/else branches or crazy, unnecessary loops when you’re already annoyed at a failing test just makes it worse. Do not couple things that really should not have an impact on each other. For instance, do not repeat search tests while logged in and logged out, unless you have a good reason.
Same goes for user types: while it is seemingly noble to try to cover different user types, do not test everything again with those. Just the cases where functionality differs
safeguard your tests against slow, problematic staging servers, but do not go so far as to mask problems with large timeout values.

Positive–Negative-tests
Fail early in your tests

If you have a problem early on, assert as soon as possible, with useful error messages;
don’t keep executing a bunch of tests that will just fail spectacularly.

fail_early

Keep a tack of all the things

Never miss any logs coming from server or on console. Be it browser log, always keep an eye on what you have observed, how it happened and consequences.

Deadlines

With a work , always comes deadline which is a means to achieve the target. I believe work, quality and timelines always go hand in hand. So keep a deadline of your own which should be not less than a day before the actual deadline.

deadlines

Keep a note of your learning

One should always check his/her own growth. By each passing day track your own learning. Write it somewhere, check related posts, try to understand the requirements more deeply and read/ask more about it.

Grow according to your own passion

On job learning is the best learning, one should always go in the direction of passion. What you want to learn, work on, that all are the factors which help you in growth. just follow yourself.

growth_passion_hand_in_hand

QA job is most innovative job, where in you can learn anything be it development(coding), devops(Continuous development), BA(Business analyst), proxy PO(Product Owner), End user, etc. So you shall be dynamic as well as alert and learning should never stop. And I tried to list down some point which can help you in learning and growing with pace.

Hope you like it!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s