Skip to content

Tester

5 ways to be A Smart Tester

Five ways to be a Smart TesterThis post will discuss 5 ways to be a Smart Tester. Testers should adopt these to work smart and gain respect but also keep your interest alive in Testing. After all, one should enjoy the work they do. So, make Testing a fun activity.

A Seasoned Tester might find Testing boring, un-interesting activity. She may find herself to reach a dead end performing same routine tasks which in no way is helping her improve her learning or adding value in her Profile.

Such a Tester starts blaming / cursing the project, the team, the application under test, the culture, the company or her astrological stars for all the wrong reasons. There’s no point of blaming others. Don’t even blame yourself.

Instead, Retrospect. See what went wrong and how you can improve to be a Valued (S.M.A.R.T) Tester. Find out ways to make your job interesting and improve learning at the same time.

 

S.M.A.R.T = Simple yet Meticulous Approach towards Realistic Testing

Continue reading

9 Good Reasons To Choose Career In Software Testing

Career ChoiceAs its rightly said, one of the most common reason to choose career in Software Testing is, “You get job easily”. But this reason creates a false hope of having a good career and a handsome salary. Speaking about “having good career” – I quit my job out of frustration.

Initial few years of my job, I did not find software testing as an exciting career option. Running the same test cases every day, Running the same automation scripts which miserably failed every time, Reporting pass fail count, Copy pasting same test cases etc. etc.. I was stuck in same boring, mundane task list forever.

And that’s when i said, “I Quit”.

Continue reading

Lessons Learned in Handling Complex Feature’s Development & Testing

complex featureIn one of my projects, there was a situation. Client proposed a new complex feature for development and wanted to promote it at the earliest. it was an important game changing feature. Now the Requirement from the client about this feature was pretty standard detailing explicit information to set this up.

On reviewing the document, I realized the Requirements weren’t very clear. I had queries. I needed more information. Meanwhile, the development team had started working on the new feature as the client wanted to roll it out within a week.

My Team Lead helped me find answers to few questions. For remaining queries, he asked me to address them to the client. Also, I communicated my concerns to the development team as well.

Continue reading

Warning : Testers may put project in trouble

Often, Testers use words, phrases without calculating the probability of putting oneself / team / project in trouble by use of such statements.

Testers should be wary of using such phrases and should not believe in them blindfold.

List that may set the bomb

I HAVE DONE COMPLETE TESTING

Do you really think its possible to do Complete Testing? Can anyone claim that the software is completely bug free? Have you tested the application in different environments, paths & combinations? Were your findings enough to cover entire testing? Have you considered all the possible scenarios? What about non-functional testing? Security, performance Testing? Different OS, browser combinations? Configuration Testing? Testing on Mobile with unending number of combinations.

Continue reading

Why Tester Needs to Ask Question?

Have you ever performed testing without asking questions? I am not referring regression testing as testing where tester may not come up with question.

James Bach’s definition of Testing is ‘Questioning a product in order to evaluate it’.

Let’s have a closer look at the process of asking questions. Testers always keep asking questions like –

Why are we testing? Who are the stakeholders? How can we determine how much testing has been done?

Continue reading