QA process in the terms of cross check

Guide Background & Objective Guide Background Тhe guide was created to expose and to gauge the common approaches to cross check, overall and in details methods and approaches to cross-check. Guide Agenda The detailed description of each step marked in cross-check list Approaches to cross-check There are some approaches to the process of cross-check.

A bit of info What do we do? Companies work with Maxymiser is to optimize their customers' online experience across all devices and channels. Our team of industry specific experts work directly with our clients to create custom optimization plans based on their business objectives and goals. How do we operate with this? - customer experience optimization - multivariate testing - personalization - cross channel optimization

A bit of info Customer experience optimization After all, consider the great lengths web marketers go to in order to collect data about their website visitors, not to mention all the time they spend poring over it in effort to predict what their customers look like, what they want, and how to best give it to them. Multivariate testing Whether a complex multivariate test across a revenue funnel, or a simple homepage A/B test, our easy to use interface will help guide you through the process to deliver a optimal website experience for your audience.

A bit of info It hasn’t been easy for ecommerce teams to get up close and personal — not for the masses, anyways. Sure, product recommendations have become popular to ‘‘personalize” shopping, so Maxymiser’s personalization suite is the answer. Personalization Cross channel optimization How does your brand look across channels? Is it 100% consistent, optimized and personalized? We’ve recognized the need to test and combine these experiences across mobile, social media and . Now, you can more accurately predict a customer’s next interest and follow-up with optimized, targeted messaging, no matter which channel they access you from.

Cross check. Whaaat? - to determine the accuracy of something by checking it with various sources. - an instance of confirming something by considering information from several sources; Cross check:

How do we do that? Step 1. Clarification and Reading of specification Let’s say in general: every specification is needed to be read at first and each point/callout/utterance etc. should be considered carefully. Step 2. Investigation the default’s behavior The next step is to research the default page rendering, it’s design, display of the elements and their functionality, the pagination and its’ correctness.

Step 3. QA of campaign’s settings It is the most capacious step from the above. Let’s divide it into smaller ones The first thing which needs to be clarified - is the generation logic and the generation method which was implemented. All these details are specified in spec, but you should check whether it is implemented and work properly The second point is URL. It is necessary to check whether campaign runs on the right URLs marked in specification. The detailed description of the steps

3.3. The 3 rd point is the segments and the optimization method. If it is indicated in the specification The next thing connected with the design and the variants’ performance. Here you should verify it. Pay attention to the copy’s correctness and it’s options: alignment, the colors, font sizes and styles. Also take a look to the image’s quality and links which were used. Try to combine default and alternative variants in order it will not break the page’s layout And the last point- a quick look to the results of Maxymiser’s affected the site’s rendering. The detailed description of the steps

Step 4. QA of functionality It is also a huge part of the cross check. You should verify that variants’ behavior and logic are working according to the spec's description and check provided user journeys/use cases in combination with variant’s description. Also you should check the use cases which were found during QA process just to be sure that all is correct. Step 5. QA of Personalization Staff In some campaign Personalization is of a big deal. We should check it in case everything is working accurately. The detailed description of the steps

Step 6. QA of user’s interaction with the client’s site This is also a step which needs special attention. As you read the specification there might be some actions which we should gather in it These might have some attributes and the value. Sometimes it encountered in dozens. Here is an example: That’s why we have to check all of them. Especially in “complex” browsers (such as IE 8*-11*, Safari 5*-7* ) and on the devices (phones and/or tablets). The detailed description of the steps

Step 7. Checking QA report The last but one step is quick view to the QA report: insure that all the possible interactions are tracked (or leave the comment about the circumstances which had prevent us from doing it), the variant performances, latency, publish instructions and default bugs which had an impact on the QA process. Step 8. Verification of publish instructions This is the last step of the cross check before the campaign’s publishing process. The detailed description of the steps

Approaches to cross-check On this slide you will find 2 ways for the cross-check. The one is based on meticulous and independent test’s review, the other - on team work but with picky and critical manner. Let’s start with the first. According to this point, QC who is responsible for cross-check, starts to investigate everything on his own. It make sense, because cross-check starts on the plane slate with a fresh look, - which is a plus. But there is some disadvantages of this approach. You might have missed some use-cases or user journeys which had occurred during QA process.

On the other hand the 2 nd way of cross-check is based on team work. During this process the person who does the cross-check makes the following steps: - read the spec - investigates the default’s behavior - check the settings of all Maxymiser’s objects - takes a look to the design and the alternative variants - tries to track the user experience and interaction with site and the last point which differs this approach from the 1 st one,- is - to collaborate with a QC - partner (the one who worked on this project) and discuss the use-cases or user journeys, details in actions’ tracking process, default issues which took place during the QA, - and find the mutual way’s of breaking something out. It is also has a positive impact on team building process. Approaches to cross-check

Alright, those were a pros. Let’s see the cons of this approach. First of all – it’s time consuming, so it will be better to use this path in sophisticated projects. The second one connected with QC’s overload. It take place when all of the QC is busy with their tasks and there is no time for the deepest analysis and cross-check. And the last one is about humans’ factor. We see that most of the people are easy going, open to change and “team-player”, but the others – are not,- they are moody, nit-picking and confrontational one’s. It is pretty hard to put up with them. Approaches to cross-check

Let’s sum up with the good and the bad sides of these approaches and try to think it over in order to decide which one is the best.. Approaches to cross-check

#ProsCons Approach #1 1.Cross-check starts on the plane slate with a fresh look You might have miss some use-cases or user journeys which had occurred during QA process Approach #2 2.Team members’ cohesion is on rise due to cooperation with a associate It’s time consuming process 3.Generates the mutual way’s of breaking something out QC’s overload. 4.Reduces the time to check on challenging projects. Characters' features of the human beings Pros and Cons

We must remember that all things are difficult before they are easy and opinions differ.. So our main goal is to find the most convenient way to cope with cross-check. Whether it is simple or not - it’s all up to you. Conclusion Good luck!

Yuliya Ryabikova, QC Phone: (097) Skype: ryabikova_ julia