- #Ordinary world definition how to#
- #Ordinary world definition Patch#
- #Ordinary world definition code#
The hero finds someone who can give him advice and ready him for the journey ahead. As you will see through the analysis and comparing of the different ideas, we can achieve much better results. However, our problem here was that for quite some time we didn’t have the whole picture.
#Ordinary world definition Patch#
Before we came up with the system, we tried to patch up the tests and find quick solutions, hoping that this way we can fix the regression problems and simultaneously be able to add new tests. The hero attempts to refuse the adventure because he is afraid. Our challenge was to find a better design so that we can refactor them and make them more maintainable, more readable and always green. Small changes in the main workflow caused almost always regression in a random group of tests. They verified big part of the system but were so brittle because they weren’t designed in a way that can be easily modified. The biggest problem for us was that we couldn’t trust our UI tests. This might be a problem or a challenge he needs to overcome. The hero faces something that makes him begin his adventure.
Sometimes all of them were green but sometimes they were problems so we needed to troubleshoot them over and over again. We had over 1000 tests that ran for over 6 hours on a single machine. This step refers to the hero's normal life before the adventure begins. There are twelve steps to the hero’s journey. I am going to tell you my "hero's story" or at least one of them. The different adventure stages are called the "hero's journey". Intrigued by mythology, author Joseph Campbell studied the myth and made the famous claim that nearly all myths, and some other story types, share common ideas and format. At the end, we will sum up everything learned. I will again shortly tell you more about the design and then compare it using the system. The second one will be about behaviours in tests. I will quickly explain what the facades are and then use the system to evaluate the design. The first example will be about facade based tests. What classes we use, how we arrange the tests.
By tests design, I mean different methods for writing end to end tests rather than boundary value analysis and so on.
#Ordinary world definition how to#
The rest of the presentation will be about giving examples how to apply the proposed system in the real world, comparing different test designs and chose the best one. After that, I will explain the concept behind each level. Then I am going to present to you the core idea about the 8 level assessment system and what for we use it. First I am going to tell you what our problems were at the beginning through- storytelling and analogies about the hero’s journey.
#Ordinary world definition code#
Also, I’m a most valuable Blogger at DZone and a MPV at Code Project.īefore we begin, just let me quickly introduce to you the plan of the talk. com where I share all my ideas about code and tests. I’m Anton Angelov, a Quality Assurance Architect. My inspiration about this talk came from the so called 'Hero's Journey'.īut first who am I. What problems we had initially and how we developed a system to solve them. My teammates and I created it specifically for our system tests design improvements.
You can find some of them in different books and blog posts but this list is unique. With a mix of personal and mythological stories I am going to present to you eight criteria for system tests design assessment. A story about heroes, lots of obstacles and the holy grail of the test automation- the perfect system tests’ design recipe.
0 kommentar(er)
