Alexa Metrics

RoboGarden’s Multiple Scenario Missions

Image showing the multiple scenario testcases

Testing a piece of software usually takes many steps and special procedures. Think about the process in an abstract way. If you want to test whether an incident happened, you may choose to test every scenario in which that incident could occur. In other words, imagine that the incident will happen in every possible environment. On second thought, you may choose to focus on only one test case and that’s it, it works. Of course, we all know that this is not reliable.

Another method is to test some random test cases or random scenarios and see how many of those passes and how many fails. Still another way to look at testing is through the method of testing itself. Are you testing the functionality of the whole system or the functionality of each part or module of the system? This is called black or white box testing.

If you decided to pursue a career in testing, you can read lots of books to grow familiar with the area. You will always arrive at certain conclusions and you can never guarantee that a piece of software is working properly by using only one test case.

The RoboGarden way

The student’s understanding of the subject matter, be it programming or anything else, is just like testing. You can never guarantee that a student fully understands a certain piece of information by asking the only one question. That’s the philosophy that has been implemented in RoboGarden’s programs.

When you begin solving RoboGarden’s missions, you will see steady progress. You will move forward easily and quickly in the earlier missions, but as you go further in the journey you will encounter harder and more sophisticated questions. Some of those questions were authored to have something called multiple scenarios.

What are multiple scenario missions?

Multiple scenario missions run the same code on more than one test case. This ensures that the code is generic enough to solve the same problem in different cases. Multiple scenario missions tell you the number of test cases that will be run.

The user can select each test case to view the environment that it will run. After the user puts in their code and clicks Run, the first scenario will run. If that scenario succeeds it’ll be marked as a success and the program will continue to the second test case. If a scenario fails, the mission will fail.

What would you take away from that? First, you must think of a complete solution, not one that is tailored to fit the first example you see. Second, you must think outside the box and always imagine, “What would happen if…?”

Got excited about testing and multiple scenarios. You can give it a try on RoboGarden. Register today for free.

Top programming languages Importance of coding education



Do you want to learn coding in less time than possible and without any money, join us on the best platform ever on learning coding as a game for kids?

Canada Flag Privacy Policy Terms of Use
Got an invite