>> GOOD AFTERNOON TO EVERYONE, MYSELF, 
ARCHANA, I HAVE SAMMY HERE, I WANT 
TO LET YOU DES KNOW THIS SESSION 
IS NOT ABOUT RSAT. I THINK I DID 
GET SOME QUESTIONS FROM THE AUDIENCE 
ASKING IF THIS IS ABOUT REGRESSION 
SUITE AUTOMATION TOOL. THIS IS ABOUT 
THE TYPE OF TESTING WE RECOMMEND 
AS PART OF THE IMPLEMENTATION LIFE 
CYCLE AND WE WILL ALSO TRY TO GIVE 
YOU SOME INSIGHT INTO SOME OF THE 
TOOLS WE WOULD RECOMMEND FOR SOME 
OF THE TESTING. SO, WITH THAT, JUST 
THE WAY WE HAVE A LIFECYCLE FOR 
DEVELOP SAG SOLUTION, THE SAME CONCEPT 
APPLIES FOR TESTING, AS WELL. I'M 
SURE YOU ARE ALL AWARE OF THAT. 
THE FIRST CRITERIA WOULD BE TO HAVE 
THE REQUIREMENTS GATHERED AND YOU 
HAVE A GOOD UNDERSTANDING OF, LEAH, 
HAVE ALL MAY QUESTIONS BEEN COVERED. 
AND IF THERE ARE DOUBTS YOU NEED 
TO CLARIFY WITH YOUR WHICH IS ANALYST, 
THOSE ARE CLEARED DURING THE REQUIREMENTS 
GATHERING ITSELF. YOU DEFINE PHOTOS 
CAN YOU, THE PRIORITY OF YOUR TESTING 
AND DECIDE AND DETERMINE WHAT YOU 
WILL BE ACTUALLY EXECUTING THESE 
TESTS AGAINST. THEN COMES THE TEST 
PLANNING, A TEST STRATEGY DOCUMENT. 
WHAT THAT LOO -- THAT SHOULD INCORPORATE 
WOULD BE ONE OF THE RESOURCES YOU 
WILL NEED. WHAT IS THE TESTING TOOL, 
WHAT WOULD WE EXECUTE THIS TEST 
AGAINST, POSSIBLY WHAT IS DOES THE 
DATA LOOK LIKE AND SHOULD YOU BE 
AUTOMATING THESE TESTS AS WELL AS 
EFFORT ESTIMATION. HOW LONG WILL 
IT TAKE TO GET THIS TESTING DONE 
AND HOW MANY RESOURCES WILL YOU 
NEED FOR THE TESTING CYCLE. THAT 
IS POSSIBLY FOR THE TESTING PLANNING 
PHASE. AFTER THAT, ENSURE YOU HAVE 
THE TEST DATA, THE TEST PLAN IN 
PLAIN AND START IN CREATING THE 
TEST CASES AND EXECUTING THEM. THE 
TESTING PHASE IS WHERE YOU WILL 
START EXECUTING THE TEST PHASES 
AND THE IDEA IS NOT JUST THAT THE 
TESTING IS NOT TO DEFINE THE DEFECTS 
BUT YOU'RE ALSO PREPARING FOR THESE 
TESTS TO THE OTHER RESOURCES IN 
THE REQUIREMENT SPACE ITSELF SO 
YOU HAVE A BETTER UNDERSTANDING 
WHAT IT IS YOU SHOULD BE TESTING 
FOR AND THAT YOU HAVE A GOOD IDEA 
AS TO, LIKE I SAID, SHOULD YOU BE 
AUTOMATING IT OR MANUALLY TESTING 
AND WHAT IS THAT EFFORT THAT IS 
REQUIRED TO GO THROUGH THE TESTING 
CYCLE. THE FINAL DATA PREPARATION 
IS WHERE THE TESTING, WHAT ARE THE 
ARTIFACTS THAT WILL COME OUT OF 
IT IT COULD BE A BUG REPORT IT COULD 
BE SOMETHING RAISED AT PART OF THE 
TESTING AND THE CRITERIA WILL BE 
TO ENSURE THE DEFECTS ARE RESOLVED 
AND YOU'RE RETESTING TO TO MAKE 
SURE THE SOLUTION IS VALIDATED. 
THIS IS ONE ROUND AND COULD BE REPEATED 
AS THE CRP CONFERENCE ROOM PILOTS 
OR TEST PILOTS. I'M SURE THIS IS 
SOMETHING ALL OF US ARE FAMILIAR 
WITH. SO WHAT ARE THE DIFFERENT 
TESTING THAT YOU SHOULD BE THINKING 
ABOUT WHEN IT COMES TO THE IMPLEMENTATION 
OF FINANCE AND OPERATIONS. IF YOU'RE 
HAVING A PART OF OUR SOLUTION ARCHITECT 
BLUEPRINT REVIEW, YOU WOULD HAVE 
US ASKING QUESTIONS ABOUT WHEN DOES 
THE STRATEGY LOOK LIKE? WHAT DOES 
THE TESTING LOOK LIKE. SO THERE 
ARE A LOT OF QUESTIONS WE COVER 
AS PART OF THAT TO ENSURE THESE 
THINGS ARE TAKEN INTO ACCOUNT EVEN 
BEFORE YOU GO LIVE. BECAUSE ONE 
OF THE THINGS THAT WE NOTICED WITH 
OUR IMPLEMENTATIONS IS THAT WE HARDLY 
SEE A PERFORMANCE BEING ACCOUNTED 
FOR WE CAN HARDLY SEE PERFORMANCE 
TESTING IN THE PROJECT TIMELINE. 
AND, IT'S ALWAYS A QUESTION AS TO, 
HEY, DO YOU DO PERFORMANCE TESTING 
AND I ALWAYS GET THE PERFORMANCE 
RESPONSE, YES, I DO INTEND. TO AND 
HOW DO YOU INTEND TO DO THAT? WE'RE 
GOING TO GET 50 USERS DOING DATA 
IN THE SYSTEM. THAT'S NOT NECESSARILY 
PERFORMANCE TESTING. SO SAM IS GOING 
TO GO INTO DETAILS ABOUT WHAT WE 
MEAN BY PERFORMANCE TESTING AND 
WHAT ARE THE DIFFERENT ASPECTS YOU 
SHOULD BE THINKING ABOUT. SEAM THING 
MIGRATED DATA. WE'VE SEEN ENOUGH 
IMPLEMENTATIONS THAT SOME OF THE 
TESTING THAT HAS BEEN DONE IS NOT 
ON THE MIGRATED DATA. YES, YOU CAN 
DO A CERTAIN AMOUNT OF DATA WITH 
TESTING, TEST DATA, BUT AT SOME 
POINT IN TIME, IF YOU PLAN TO SPRING 
IN HISTORICAL TRANSACTIONS OR OPENING 
BALANCES FROM THE LEGACY SYSTEMS, 
MAKE SURE YOU'RE DOING A CERTAIN 
AMOUNT OF TESTING ON THAN MIGRATED 
DATA, AS WELL. ANOTHER COMMON THING 
WE SEE IS SECURITY. ALMOST ALWAYS 
TESTING WITH THE RIGHT SECURITY 
ROLES ARE ALWAYS LEFT TO THE LAST. 
THAT IS SOMETHING WE KEEP INSISTING 
DURING OUR REVIEWS, AS WELL, TO 
MAKE SURE THAT SECURITY RULES ARE 
ASSIGNED AND TESTING IS DONE WITH 
THE RIGHT SECURITY RULES IN THE 
EARLIER CYCLE ITSELF. PRETTY STRAIGHT 
FORWARD, IT SHOULD BE SOMETHING 
THAT ALL OUR CUSTOMERS SHOULD BE 
DOING RIGHT BEFORE GOING LIVE. IT 
COULD BE DONE IN THE UAT, AND MICROSOFT 
PROVIDES WITH THE SUBSCRIPTION OR 
IT COULD BE DONE IN YOUR PRODUCTION, 
IF YOU HAVE ALL THE ARTIFACTS, WE 
DO ALLOW IT 30 TO 45-DAYS BEFORE 
YOU GO LIVE. YOU COULD TO THE TEST 
ORG SMOKE TESTING IN PRODUCTION 
IN SUCH A MANNER THAT YOU CAN ALWAYS 
ROLL BACK THE DATA USING POINT IN 
TIME RESTORE. SO THOSE ARE SOME 
OF THE ASPECTS FROM AN IMPLEMENTATION 
POINT OF VIEW WE CALL OUT AS, HEY, 
THESE ARE SOME OF THE THING US SHOULD 
BE TESTING. THE LAST POINT IS REGRESSION, 
AND IF YOU'VE BEEN ATTENDING SOME 
OF THE SESSIONS, YOU MIGHT HAVE 
HEARD OF ORDER NEW OFFERING, THE 
REGRESSION TOOL. IT COULD BE AN 
EXISTING TOOL YOU ONLY HAVE IN HOUSE 
BUT WITH THE ONE VERSION AND CONTINUOUS 
UPDATE JOURNEY WE ARE ON WHERE WE'RE 
RELEASING MONTHLY UPDATES, YOU HAVE 
TO PICK UP AT MINIMUM TWO UPDATES 
PER YEAR. SO ESSENTIALLY YOU STILL 
NEED TO PLAN FOR SOME SORT OF REGRESSION 
TESTING CYCLE OR REGRESSION TESTING 
TOOL IN THE IMPLEMENTATION JOURNEY 
FOR FINANCE AND OPERATION. SO, AGAIN, 
THE REASON WE BRING THIS UP IS PLANNING 
FOR ENROMINS. ONE IS PRODUCTION, 
SOMEONE A SAND BOX AND THE TEST 
UM NEED TO PLAN FOR, IF YOU ARE 
A CUSTOMER, PLAN FOR THAT OR IF 
YOU ARE A PARTNER, PLAN WITH YOUR 
CUSTOMER TO ENSURE THAT YOU UNDERSTAND 
HOW MANY ADD ONS ARE REQUIRED AS 
YOU MOVE FORWARD IN THE IMPLEMENTATION. 
TO UNDERSTAND HOW MANY ADD ONS ARE 
REQUIRED YOU NEED TO UNDERSTAND 
THE ENROLLMENT. THE POSSIBILITY, 
THE TRAINING COULD BE REUSED FOR 
FUNCTIONAL TESTING. THERE IS A CHANCE 
ONCE THE FUNAL DATA IS COMPLETE, 
YOU MIGHT USE THAT FOR ENROLLMENT 
TESTING. BECAUSE WE DO ALLOW ADD-ONS 
OF DIFFERENT TIERS. IF YOU'RE FAMILIAR 
WITH THE TEARS IN OUR SUBSCRIPTION, 
YOU KNOW EACH TIER HAS A DIFFERENT 
STRUCTURE. AGAIN, THE ENROLLMENT 
STRATEGY, PROVIDES HIGH FLEXIBILITY 
AND SPEED AND QUALITY OF IMPLEMENTATIONS. 
FROM A SOLUTIONS POINT OF VIEW, 
WE WOULD SAY VALIDATE ON THE UAT, 
SORRY, THE UAT SHOULD BE DONE OR 
VALIDATED ON A TIER 2 OR EYE HIGHER 
THAN TIER 2 ENROLLMENT. THE REASON 
IS TIER 2 ONWARD IS A SQL AZURE 
THAT IS MORE COMPATIBLE OR COMPARABLE 
WITH OUR PRODUCTION. DOING ANY TESTING 
ON TIER 1 IS A DEFINITE YES ARE 
FOR US TO SAY WE CANNOT DEPLOY PRODUCTION 
FOR YOU. WHEN WE DO A PRODUCTION 
DEPLOYMENT READINESS REVIEW, WHEN 
WE KNOW YOU'VE DROP YOUR TESTING 
IN TIER 1, UNFORTUNATELY THERE IS 
NO WAY TO TELL YOU GOING AHEAD WITH 
PRODUCTION DEPLOYMENT, WE WILL NOT 
BE ABLE TO DO THAT. THAT IS THE 
REASON TO MAKE SURE UAT IS PERFORMED 
ON TIER 2 OR HIGHER ENROLLMENT. 
TEST THE REAL LIFE SITUATIONS, THIS 
IS TO AUTHENTICATE, A LOT OF TEAMS 
PERFORMANCE TESTING OR FUNCTIONAL 
TESTING INVOLVED TESTING THE SCENARIOS 
INDEPENDENTLY. YOU WILL TEST INTEGRATION 
INDEPENDENTLY AND BATCH DIFFERENTLY 
TO MAKE SURE IT WORKS BUT A LOT 
OF TEAMS IT IS NOT DONE IN THE SAME 
SEQUENCE HOW IT WILL BE DOING IN 
PRODUCTION. WE RECOMMEND A DAY IN 
THE LIFE, ESSENTIALLY WHAT WE'RE 
LOOKING FOR IS MAKING SHOE THE INTEGRATIONS 
BATCH, ALL OF THESE ACTIVITIES ARE 
CONDUCTED IN UAT AT THE SAME FREQUENCE 
AND DATA IT AS WILL BE DONE IN PRODUCTION. 
DON'T IMPLEMENT OUTSIDE OF THE SUBSCRIPTION. 
THIS IS MOSTLY COMING FROM THE REASON 
IF YOU CAN KEY PLOY ENROLLMENT GUESS 
YOUR OWN SUBSCRIPTION, ALL OF THAT 
ARE AT THE END OF THE DAY SQL SERVER 
SO NONE HAVE AN INFRASTRUCTURE COMPARABLE 
TO THAT OF PRODUCTION EQUAL TO AZURE. 
THE ONLY WAY YOU CAN DEPLOY A HIGH 
AVAILABILITY ENROLLMENT IS THROUGH 
THE MICROSOFT SUBSCRIPTION. SO DO 
NOT IMPLY MOMENT OUTSIDE OF THE 
SUBSCRIPTION. THE PERFORM MEASURES 
AGAINST TIER 1S ARE NOT GOING TO 
BE RELEVANT. I DON'T THINK SO WE 
HAVE ANY CUSTOMERS DOING THIS AT 
THIS STAGE, BUT THE INITIAL FACES 
WE HAD A LOT OF CUSTOMERS TRYING 
TO DO INTEGRATION TESTING WITH TIER 
1. IT WAS PERFECTLY FINE, THE MOMENT 
THEY MIGRATE TO UAT, THEY START 
RUNNING INTO ISSUES BECAUSE THE 
INTEGRATION CONNECTIONS ARE NOT 
NECESSARILY GOING TO BE THE SAME 
WHEN YOU'RE TRYING TO CONNECT FROM 
A SQL AZURE, FOR EXAMPLE. SO ALL 
OF IT IS JUST TO LET YOU KNOW, TRY 
TO MAKE SURE, IT IS MANDATORY TO 
MAKE SURE YOU'RE ACTUALLY DOING 
YOUR UAT OR YOUR TESTING ON A TIER 
2 OR HIGHER. IN TERMS OF THIS LAST 
POINT IS JUST TO MAKE SURE THAT 
IT IS IMPORTANT THAT NOT JUST A 
PARTNER BUT THE CUSTOMER RESOURCES 
ARE ALSO EQUALLY FAMILIAR WITH THE 
STEPS THAT NEEDS TO BE TAKEN WITH 
RESPECT TO SERVICES ANALYSIS. SOME 
OF THESE PROCESSES ARE NOT SOMETHING 
THE CUSTOMER IS FAMILIAR WITH. AS 
A PARTNER, ONCE YOU STEP OUT, THERE 
IS A GOOD CHANCE YOU'VE SEEN CUSTOMERS 
STRUGGLING WITH THE PROCESSES WITH 
RESPECT TO SERVICES. THE LAST POINT 
IS GET THE BUSINESS SIGN OFF, TO 
MAKE SURE ALL THE PARTIES INVOLVED 
ARE ALL ON THE SAME PAGE IN ALIGNMENT 
WITH WHAT HAS BEEN TESTED, WHAT 
IS NOT TESTED. AND IF THERE ARE 
THINGS THAT ARE NOT COMPLETELY TESTED 
THERE MULTIPLE PHASES OF GO LIVE. 
WHAT ARE PRESIDENT NEXT GO FORWARD 
STEPS THAT YOU NEED TO TAKE ONCE 
THE CUSTOMER GOES LIVE THERE COULD 
BE SCENARIO US NEED TO TEST POST 
GO LIVE. OR THERE COULD BE AREA 
US NEED TO KEEP AN EYE ON, FOR EXAMPLE, 
ONCE YOU GO LIVE, IS THERE A CHANCE 
THAT THE BUSINESS DATA WALL IS GOING 
TO INCREASE. IF YES, SHOULD THE 
BATCHES STILL BE IN THE SAME PLACE 
THEY ARE AT THIS STAGE. THERE IS 
A GOOD CHANCE YOU ARE PROBABLY HAVING 
A FREQUENCY OF EVERY HOURS, MAYBE 
A BATCH PROCESS IS RUNNING. WHEN 
THE DATA WALL LIMIT INCREASES SHOULD 
THEY STILL BE RUNNING? THOSE ARE 
SOME OF THE ASPECTS YOU NEED TO 
THINK THROUGH AND GET THE BEST SIGN 
OFF SO IT IS NOT JUST ABOUT TESTING 
BEFORE GO THRIVE IS MAKING SURE 
YOU'RE PLANNING FOR AFTER GO LIVE, 
AS WELL. ON THAT NOTE, I'M FOG HAND 
OVER TO SAMMY. >> THANK YOU. THANK 
YOU, ARCHANA. WE'LL JUST TRY TO 
DIG IN A LITTLE BIT OF THE FIRST 
KIND OF TESTING, WHICH ARE UNIT 
TESTS. OH, SORRY. IS THIS BETTER? 
THANK YOU. DO YOU HARE ME? OKAY. 
-- HEAR ME? OKAY. FOR UNIT TESTS, 
WE FIRSTLY WANT TO SAY THAT THIS 
IS A DEVELOPER-ORIENTED KIND OF 
TEST. WE SELL MULTIPLE PROJECTS, 
AS IT SAYS, PEOPLE USING IT TO GENERATE 
SOME CLASSES TO USE THEM AS A UNIT 
TEST CLASSES. THIS IS DIFFERENT 
AND NOT POSSIBLE AS A UNIT TEST 
BECAUSE THIS IS A BUSINESS CYCLE 
TEST AS IT IS COMING FROM THE UI. 
FOR THOSE WHO ARE RECORDING THAT 
KIND OF PROCESSES, WE SHOW DIFFERENTLY, 
TELL YOU TO USE THOSE RECORDING 
WITH RSAT. THIS IS A TOOL WHICH 
IS NOT BASED ON DEVELOPMENT BUT 
ON RECORDING AND WHICH WILL GIVE 
YOU END TO END TESTS. FOR UNIT TESTS, 
THE IDEA IS TO TEST SPECIFIC METHODS 
OF CLASSES AND TO ENSURE AND TO 
INCLUDE THEM IN A BUILD AUTOMATION 
SO EVEN IF YOU CHANGE YOUR CODE 
ALL THE TIME, YOUR METHOD IS STILL 
WORKING. ONE OF THE CONSTRAINTS 
WE ARE SO VERY OFTEN, WE SEE VERY 
OFTEN WITH UNIT TESTS ARE RELATED 
TO THE COUPLING OF DATA. IF YOU 
HAVE YOUR TESTS, WHICH ARE BASED 
ON DATA WHICH ARE IN THE DATABASE, 
IT'S QUITE HARD TO ENSURE THAT THOSE 
TESTS WILL REMAIN RELIABLE AND VIABLE 
IN THE FUTURE BECAUSE DATA CAN EVOLVE. 
SOME SOLUTIONS CAN BE BASED ON SOME 
COMPLEX BUILDING PIPELINES, BASED 
ON DATABASE RESTORE, ET CETERA. 
ONE OTHER POSSIBILITY IS TO USE 
WHAT WE CALL SIS-FAKE. A PACKAGE 
AVAILABLE IN THE ENVIRONMENTS AND 
WHICH ALLOWS TO YOU SIMULATE THE 
BEHAVIOR OF A SPECIFIC STANDARD 
TO RETURN WHATEVER YOU WANT EXACTLY 
AS THIS IS DONE IN MORE CLASSICAL 
WEB DEVELOPMENT. THIS WILL GIVE 
YOU ABILITY TO DECOUPLE YOUR UNIT 
TEST FROM YOUR DATA AND MAXIMIZE 
THE CHANCE TO KEEP YOUR TEST RELIABILITY 
DURING THE BUILD. OF COURSE, THE 
SLIDE SHOWING IF YOU INTEGRATE THIS, 
YOU WILL HAVE REALLY EARLY EVENTUALLY 
REGRESSIONS. FAR BEFORE FUNCTIONAL 
TESTING, WHICH CAN BE COSTING. THE 
SECOND KIND OF TEST I WOULD LIKE 
TO HIGHLIGHT ARE THE INTEGRATION 
TESTING. FOR THOSE ONES, WE SHALL 
DISTINGUISH TWO KINDS OF INTEGRATION. 
THE FIRST IS IS SYNCHRONOUS. I DON'T 
KNOW IF YOU KNOW, WE'RE NOT COVERING 
THAT SECTION BUT THERE ARE MULTIPLE 
WAYS TO DO THAT. ONE OF THEM IS 
TO BUILD YOUR OWN WAY, USING TOOLS 
LIKE LOGIC APPS WHICH ALLOWS YOU 
TO CALL YOUR API, YOUR ODATA API. 
THE OTHER WAY IS TO USE SOME TOOLING 
IN THE MARKET WHICH CAN JUST GET 
THE, IT CAPTURED THE TRAFFIC AND 
REPLAYS IT. THAT GIVES YOU AN EASY 
WAY JUST TO CAPTURE WHATEVER YOU 
WANT AND TEST THE VOLUME YOU WANT 
BY REPLAYING THOSE SCENARIOS. A 
LOT OF TOOLS IN THE MARKET DOING 
THAT. AND THAT'S A POSSIBLE SOLUTION 
TO EVENTUALLY SIMULATE PEAK VOLUMES, 
SIMULATE THE DATA TEST, EST. TEST, 
EST. , ET CETERA. THE THIRD TESTING 
PROTOCOL WE WANT TO HIGHLIGHT IS 
THE PERFORMANCE TEST SCENARIO. THE 
MOST IMPORTANT THING HERE IS TO 
TRY TO MIMIC WHAT WILL HAPPEN. THE 
APPLE OF THIS IS TO NOT BE SURPRISED 
ONCE THE ACTION WILL BE RELEASED 
AND DETECT ISSUES REGARDING PERFORMANCE 
TOO LATE. AND TO ACHIEVE THAT, THERE 
IS A MICROSOFT PROVIDES. NOT SURE 
ALL OF YOU ARE AWARE BUT WE'VE UPDATED 
THE DOCUMENTATION FOR PERFORMANCE 
AS DK LAST WEEK AND WE'RE PROVIDING 
A DETAILED GUIDE TO HELP YOU SET 
UP MULTIUSER TESTING ICING FROM 
AZURE TEVOPS, WHICH MEAN IT IS SIMULATES 
YOUR WORKLOAD FROM DEVOPS. YOU SHOULD 
GO THAT WAY. ANOTHER THING ALSO 
IS TO TRY SIMULATE THE REAL BEHAVIOR 
OF YOUR END USERS. I MEAN, DURING 
YOUR ACTION, YOU SHALL TRY PROBABLY 
TO BUILD IT STEP-BY-STEP. FIRST 
FOCUS ON THE MOST CRITICAL FLOWS 
YOU HAVE AND DO IT STEP-BY-STEP. 
DON'T TRY TO COVER ALL YOUR PROCESSES 
FROM A PERFORMANCE POINT OF VIEW, 
IT DOESN'T MAKE SENSE. MOST OF THE 
ACCESSORY FEATURES ARE JUST USED 
BY ONE OR TWO USERS AND WE NEVER 
PRESENT ANY ISSUE OF A PERFORMANCE 
VIEW. YOU SHOULD TRY TO FOCUS ON 
REALLY WHAT YOU THINK IS A POTENTIAL 
RISK FROM A POINT OF VIEW. I THINK 
I JUST SUMMARIZED THIS SLIDE ABOUT 
PERFORMANCE TESTING. DEFINE FIRST 
YOUR OBJECTIVES, THEN DEFINE YOUR 
SCENARIO. WHEN 88 SAY DEVELOP, DESIGN 
YOUR TEST, IT IS MUCH MORE USING 
THE DK, YOU SHOULD RECORD THE SCENARIO 
YOU WANT AND ADAPTED CLASSES TO 
GENERATE THE VOLUME YOU WANT. AND, 
THEN, YOU CAN SIMULATE YOUR -- YOU 
CAN SIMULATE EVENTUALLY IF YOU WANT 
A HIGH VOLUME OF DATA USING DATA 
EXPANSION TOOL, A TOOL PROVIDED 
WITH FNO. AND THEN YOU CAN EXECUTE 
YOUR TESTS AND OF COURSE YOU HAVE 
TO MONITOR IT TO ENSURE THAT YOU'RE 
HAVING THE LEVEL OF PERFORMANCE 
YOU WANT. THE LAST KIND OF TESTING 
YOU WOULD LIKE TO FOCUS ON IS THE 
END TO END TESTING, AND DEFINITELY 
THIS SECTION HAS TO BE -- THIS IS 
OURRIES, IT ADVICE. IT GIVES US 
THE ABILITY TO RECORD END TO END 
SCENARIOS, PLAY THEM AND HAVE DETAILS 
ON WHAT CAN BE THE ERRORS, YOU CAN 
VALIDATE THE RESULTS OF YOUR STEPS, 
NOT ONLY RUNNING BUT THE VALIDATION 
OF WHAT YOU ARE DOING AND YOU CAN 
CHANGE THE TEST. YOU CAN ALSO USE 
A USER CONTEXT ON YOUR RECORDING 
BY SETTING THE E-MAIL FOR USER TO 
ENFORCE HIS OWN SECURITY RULES AND 
TO TEST IN REAL LIFE SCENARIOS. 
AND WITH THIS PICTURE, WE SHOULD 
HAVE COVERED ALL THE IMPORTANT TESTING 
SCENARIOS WE SHOULD COVER. I THINK 
THAT'S ALL FOR US. WE HAVE TO SHARE 
WITH YOU THIS SLIDE, PLEASE GIVE 
US YOUR FEEDBACK. WE'RE REALLY INTERESTED 
AND IT IS IMPORTANT FOR US. THANK 
