Puzzle - Help the captain

In the year 2050 Captain Morgan and his crew are stuck midway development/testing for the next huge OSv5.1 release for their spaceship Jatayu.

The problem they are stuck at is:

To verify correctness of the results returned from a black box calculator
Procedure the crew follows:

1. Answer close to 40 questions [Please note: The questionnaire can have drop down menus, radio buttons, and relationships within questions (some questions will be displayed if a specific question is answered)]
The captain of the ship has signed an NDA and cannot share the questions
2. The answers are fed into a Black Box (Calculator)
3. The results are displayed on the screen

Assistance offered:
Black illusionists have agreed to verify if the values fed into their Black Box are correct or not. But they will check only 25 combinations (we supply inputs to each question and the actual results). They will annihilate us if we exceed the magic figure of 25.

Strategies suggested by Problem Squealers in the crew team:

1. Pick 25 random values returned by answering the questions to the Black illusionists and verify the results.
2. Discuss with the merchants and prioritize the most common 25 scenarios with realistic answers to the questions, and then have them verified by the Black illusionists.
3. Invest time to mechanize all possible combinations. Run the automation suite. Choose 25 weird values and get them verified by the Black illusionists.
4. Broadcast the risks to the Kingdom and follow idea 2.

Captain Morgan, though happy, is not assured with ideas from his crew. He now invites citizens of Planet Earth for help.

Can you help Captain Morgan?

Comments

Post a Comment

Popular posts from this blog

Exploratory testing, Session based testing, Scripted testing…concertedly

In my last assignment a mix of exploratory, session based and scripted testing helped won an award, appreciation by managers & stake holders at our organization. The quotes from our award certificate “ QA team has come up with some intelligent testing techniques to validate the product. The customer test team was not able to find even a single critical bug after delivery ” Though the award was a small one in terms of the award categories our organization have, it meant a lot to me and the team, because this was the first time the team used exploratory approach. The assignment was not pure exploratory or session based, in fact it was supposed to be scripted, but a mix of all three exploratory, session based and scripted testing helped us learn, enjoy, and meet our mission. The assignment started off with developing test cases. We wrote test cases based on the initial requirement document provided. We did come up with a large number of test cases, of which most were re-written, some
Read more

What do you do when you find a bug?

What do you do when you find a bug? Hold on do not answer it right now. Let me first set the context. You are part of an agile team. The developers sit opposite to you. You are testing a feature in a session. You are time bound and have the good habit of capturing notes when you test. When you now find a bug what do you do? Assuming that you have taken enough notes you go on to write a good bug description and may capture a screen shot, video of the bug and continue with your session. At the end of the session do you Open the defect tracking tool (wait for it to load), enter all the fields for a bug, upload necessary evidence and have the tool share the defects with your dev team? Or Open the defect tracking tool (wait for it to load), enter all fields for a bug, upload necessary evidence and then compose an email to the dev team with the bug id’s/descriptions? Or Walk to the developer share your notes; reproduce it if required, work together to identify the problem? I work in
Read more

Regression Checks + Regression testing = Regression testing?!

One of the questions I find hard to answer when I use exploratory test techniques in my project is,”How do you run regression tests? How do you prioritise them? Do you automate them? Do you document regression test cases?” And then a bunch of questions follow. Let me define the context. I work closely with developers; we use either Scrum or Kanban - which ever best suits our project, product owner, business. We do not believe in individual metrics, blame games, stringent processes, and heavy documentation. All we care about is to deliver high quality software. This does not mean that there is no process, metrics or documentation. We have them all, but they are there to meet our needs and to help those who will come onboard to support/maintain the software. Regression Checks At the start of a story, testers pair up with developers to develop feature files using SpecFlow. Some call it Acceptance Test Driven Development and others Behaviour Driven Development [I am yet to figure out the d
Read more