We have answers everywhere!

I have been experiencing lots of positive thoughts around me while I also create so. People have been asking me lots of questions which many of them have already spoke about it. And I believe the only reason they are unable to understand is because, they are not doing the way they wanted to. The moment we start encouraging people to put their own thoughts and start to help them improvise on that is the only way to align the goal.

Here is something interesting that I found when I was studying about CDT (Context Driven Testing).

I used “BING” search for the only reason that I was using Internet explorer and my default search engine was Bing. I tried the same phrase (Define Context) on various search engines, like Google, Ask etc.

I observed something interesting that no other search engine game me this result.

Bing Search Result for "Define context"

Bing Search Result for “Define context”

I am not trying to compare or test which one of the engine gives me a good result. I found something that I was looking for!

  • Structure
  • Framework
  • Context
  • Scheme
  • System
  • Plan
  • More

Right, now relate it to your work.

 

 

 

Context Synonyms itself defines the process. This is not the only process, this is also the way we can look and relate. Now that I found this result and I solved few questions of mine. I just wanted to share it with my readers.

Help Testers to learn about “How” and not “Here is how”.

Thanks.

“Test” Crash Investigation

Hello Readers,

I would like to share few of my moments that I thought has a huge connection between the way we are and the way we are supposed to be. I have been watching Air crash investigation since the age of 11, no matter I understood or what. But it has always been interesting for me to watch every episode of it.

 

Investigation seemed “Testing after” the risk arrival for me

 

The investigation that takes place after every complex incidents has been vital and crucial clue for every accidents that could happen as a chain reaction. Ever since the “Bug” is found and reported has helped to evolve every part of aviation, clearly a new dimension of testing for every risk that takes place.

For Air crash investigation, every part of the plane and every clue could help them understand the whole of the problem and could solve / change the architecture. The investigators have been articulating every moment, coming up with great ideas, emulate the process of the accident. This gained more attention to me, exactly, every part of it is crucial and even a slight change would end up in severe loss of life.

While computers play majority role of aviation. It is split into 2 different errors that could generally happen. “HUMAN (Pilot) ERROR” and “SYSTEM ERROR” and the same with everything in this world.

We have been testing softwares that is being used by millions and has huge impact over the peoples emotion, business, market etc. While we have everything under our control before it impacts 100 whereas, it’s not the same with aircraft. The simultaneous decision making and different levels of plan help the pilots to enter the safe zone.

It’s no different from 100 people death

  • Recover black box (Flight data recorder)

Our backbox is nothing but our test design. While our product is live and observe a high severity bug. Our black box  should help us determine where exactly our data has been misplaced, the missing piece of our design may have caused this bug, we recover them and crack the puzzle of fixing them.

  • Proofs & witnesses

Well, sometimes we testers convey a bug to the developers / the team and not really document them. There has to be some proof with few acceptance from the opposite party in order to be really precise and may help finding the clue of happenings.

  • Join the pieces

While the investigators tried to put the whole of the plane to understand the cause. We would want to join the pieces of information and to determine and help our business understand the severity, while we do that we also clear up the priorities by eliminating the unrequired factors. This is the approach that every investigator would take to solve the problem.

  • Specialization

As there are more than a factor and fields that would need investigation, for example: “Bird strike” on On September 22, 1995 boeing hit by bird lost both of it’s engine and lead to a huge disaster while there were 50+ accidents happened in the name of bird strike, this one was unique. It was hit by a lightweight goose with the difference in the structure of it’s bone caused this incident. This particular scenario needed different level of expertise, Biology. Finding the right expertise at the right time could distinguish the matter of time, plan and the accidents.

  • Take off and landing

While most of the flying is taken care by the aeroplane itself, it always needs human effort on landing and takeoff. The value that human defines is critical, no matter what! Humans are blamed finally and not the system. Even when the system is blamed and is being designed by human. We define the system and not allow machines to overwrite.

1st aircraft designed by Air france which was designed to overwrite human inputs. This took away 30+ lives On 26 June 1988. However, this particular went through lots of crisis and political matters the fact that the overwriteand the delay in flights reaction led to this incident. You could watch the episode here.

  • Team and reporting

Investigators have an habit of dividing the task specific to specific person as they could get the coverage & to near the solution with given and estimated time. This gives them a whole lot of power to explore the deepest and widest. Clearly the best way to tackle the problems. Our team and tasks decides the coverage and depth of our investigation towards solving our customers problem.

  • Reporting and conclusion

After months of investigation, the final report from different sources with great insight and highlight of the problem that was found in the aircraft which is responsible for the problem has to be really precise and impact over different organization, methods, design and practices with compared to the existing ones.

Everything should change over the period of time

  • Recognition and penalty

Investigators are often punished for the reaction in which the problem was handled, unexpected and inevitable. While the opposite of it has to be praised to which the story of theirs become lessons to others.

I am always interested in Air-crash investigation and I would want to do it one day (Soon or then). However, I am already an investigator helping my customers understand the risks and various influential factor. I have been practicing by picking up a crash / accident, come up with scenarios / stories / tools / possibilities etc and this had helped me improve in several areas.

Thank you for reading this post. Comments and suggestions are welcomed.

Have a great day!

 

Fundamental for becoming a REAL software tester

I could start by keeping my title as “Good software tester” but I believe good has no meaning when it comes to reality. I define REAL as “Things that really exist”.
I believe in existence. I believe in testing existing everywhere.

I see lots of people getting into testing and takes time to for them to understand and take their own steps forward, of course with great guidance you can become a REAL one to. I have been into testing for more than 1 1/2 years in REAL but I would say that every people in this world are testers indirectly and very few people choose the right path.

I believe, hope and experimented things that’s written below. I also believe in questioning ourself from the beginning of our career.

1. Worry for things that we really need to worry about!

We humans, easily get disappointed and we keep remembering that very often and as a impact of this, we easily quit certain things even if we are being provided with an opportunity. It’s like “ruminant digestive method”! We keep worrying about things and don’t see real value worrying about it. Chuck it and continue!

2. Celebrate disappointment

Hey, you got objurgations from your manager?? Alright, go have a beer by keeping a break point. Problems are real challenges in our life. Try to get into more complicate problem (Oops, you really don’t have to get in) and find the previous problem to be very simple! Try it 😉

2. Brain needs to be taught not the mouth

Ya, I have come across this problem. I have been a great example of this. I speak, I speak a lot, I speak a lot, useless! I once realized, dude you are just like some useless post on Facebook. People see it and really worry about it. So, I started reading, practice instead of talking and on trying to impress others.

3. Be in every nook and corner

If you really want to understand, learn and be creative while you test? You have be like CCTV camera. Read / write blogs, Follow some great tester on Twitter and follow up the conversation, also join them. Attend all conferences, in fact all developer conferences if you can, it helps testers to be more productive and informative while you test and report!

4. Crack the heuristic

Life is full of puzzles and not only life, even testing is. While we are solving our customer problems by helping them understand their risks, there are areas that you are already using heuristic are not actually aware of! We might have to go slow or observe the flow in which you are solving the problem and you finally end up cracking whole lot of things. I recently found one,” The problem in testing is not really testing, it’s the process that needs refinement”. (Maybe people have already written about it, but it’s important for us to experience and crack it!)

Hey, I remembered this, Check out my friends: Heuristic post by Dheeraj karanam.

5. Find what you are good at

Every individual have their own goods. We don’t actually figure it out easily, it takes time.  It needs some observation and comes out with comparison. Be courageous to tell everybody about your ideas, way you want to test, your style of reporting but have one! Share everything you have.

6. Track and fight your progress

Its quite hard as a fresher or from the beginning of the career. Taking progress isn’t easy! But personally, tracking my progress in several ways. Self assessment, reports, sense of questioning, knowledge, comparison etc. However, don’t jump into conclusion based on the progress. We might have to push things slowly to make it work. Talk to anyone and everyone!

7. Connect the dots

As a tester, I think it’s important to think panoptic, we have got lots of things to put in comparison, make different people take decisions. Hundreds and thousands of people gonna use the product that we are are testing or going to test. Try to connect things that are happening in reality.

8. You are responsible for yourself

You got screwed?? so what, you did it! Tell the truth, it makes you stronger and harder for other to face you. Take responsibility but keep it simple. Responsibility doesn’t mean that you have to run a team telling others to work the same way you want to. You heard it right “You are responsible only for yourself. Mistakes are meant to be made and not to repeat them!

9. Find the patterns

Patterns are everywhere. As testers, if we crack the patterns with the product that we are testing. I believe that’s the REAL value that we can add to our customers. Patterns are not only with the product that you are testing, it’s on everything you look and do!

10. Take a break

It’s important for your brain to take rest. You will understand everything that I have written above when you sit in a part thinking about “what the hell is happening to me”.

There are whole bunch of things that we as a tester and human being have to concentrate about. But it’s very difficult for us to understand and observe everything. We are all running around all the situations. However, if we don’t understand certain things. It will become hard for us to differentiate on exactly the situation with what we want to learn. I believe this is the beginning of certain things as a part of our learning and it’s very few!

Guess what, I was watching iron man while writing this post.! 🙂

Simplest things are the ones which is really hard to figure it out and fix!