regenerated schedule

Signed-off-by: René <[email protected]>
robotframework · Dec 14, 2023 · 8716607 · 8716607
1 parent 60d3106
commit 8716607
Show file tree

Hide file tree

Showing 6 changed files with 10 additions and 10 deletions.
diff --git a/dist/js/app.604e1725.js b/dist/js/app.604e1725.js
diff --git a/dist/js/app.77654663.js b/dist/js/app.77654663.js
diff --git a/...ifest.362e5522104d4f0908618c7ef98fa762.js → ...ifest.6814a3d5f38016b0367f2803d5c2fb59.js b/...ifest.362e5522104d4f0908618c7ef98fa762.js → ...ifest.6814a3d5f38016b0367f2803d5c2fb59.js
@@ -4,7 +4,7 @@ self.__precacheManifest = (self.__precacheManifest || []).concat([
     "url": "dist/404.html"
   },
   {
-    "revision": "e409d7d9a077cf4fbd0c",
+    "revision": "81b206a9ea165ab5423b",
     "url": "dist/css/app.8837a484.css"
   },
   {
@@ -188,12 +188,12 @@ self.__precacheManifest = (self.__precacheManifest || []).concat([
     "url": "dist/img/ticket-depth.jpg"
   },
   {
-    "revision": "95a6378e5902d793ce55ef720cfceeb5",
+    "revision": "73805d4674f6eff827648102b354deaa",
     "url": "dist/index.html"
   },
   {
-    "revision": "e409d7d9a077cf4fbd0c",
-    "url": "dist/js/app.77654663.js"
+    "revision": "81b206a9ea165ab5423b",
+    "url": "dist/js/app.604e1725.js"
   },
   {
     "revision": "71fe642c6ceae86d8cdc",

diff --git a/dist/service-worker.js b/dist/service-worker.js
@@ -14,7 +14,7 @@
 importScripts("https://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-sw.js");
 
 importScripts(
-  "dist/precache-manifest.362e5522104d4f0908618c7ef98fa762.js"
+  "dist/precache-manifest.6814a3d5f38016b0367f2803d5c2fb59.js"
 );
 
 workbox.core.setCacheNameDetails({prefix: "robot-framework"});

diff --git a/index.html b/index.html
@@ -17,4 +17,4 @@
               l.pathname.slice(0, -1) + decoded + l.hash
           );
         }
-      }(window.location))</script><link href="dist/css/app.8837a484.css" rel="preload" as="style"><link href="dist/js/app.77654663.js" rel="preload" as="script"><link href="dist/js/chunk-vendors.6e0fb070.js" rel="preload" as="script"><link href="dist/css/app.8837a484.css" rel="stylesheet"><link rel="icon" type="image/png" sizes="32x32" href="dist/img/icons/favicon-32x32.png"><link rel="icon" type="image/png" sizes="16x16" href="dist/img/icons/favicon-16x16.png"><link rel="manifest" href="dist/manifest.json"><meta name="theme-color" content="#4DBA87"><meta name="apple-mobile-web-app-capable" content="no"><meta name="apple-mobile-web-app-status-bar-style" content="default"><meta name="apple-mobile-web-app-title" content="robot-framework"><link rel="apple-touch-icon" href="dist/img/icons/apple-touch-icon-152x152.png"><link rel="mask-icon" href="dist/img/icons/safari-pinned-tab.svg" color="#4DBA87"><meta name="msapplication-TileImage" content="dist/img/icons/msapplication-icon-144x144.png"><meta name="msapplication-TileColor" content="#000000"></head><body><noscript><strong>We're sorry but robot-framework doesn't work properly without JavaScript enabled. Please enable it to continue.</strong></noscript><div id="app"></div><script src="dist/js/chunk-vendors.6e0fb070.js"></script><script src="dist/js/app.77654663.js"></script></body></html>
+      }(window.location))</script><link href="dist/css/app.8837a484.css" rel="preload" as="style"><link href="dist/js/app.604e1725.js" rel="preload" as="script"><link href="dist/js/chunk-vendors.6e0fb070.js" rel="preload" as="script"><link href="dist/css/app.8837a484.css" rel="stylesheet"><link rel="icon" type="image/png" sizes="32x32" href="dist/img/icons/favicon-32x32.png"><link rel="icon" type="image/png" sizes="16x16" href="dist/img/icons/favicon-16x16.png"><link rel="manifest" href="dist/manifest.json"><meta name="theme-color" content="#4DBA87"><meta name="apple-mobile-web-app-capable" content="no"><meta name="apple-mobile-web-app-status-bar-style" content="default"><meta name="apple-mobile-web-app-title" content="robot-framework"><link rel="apple-touch-icon" href="dist/img/icons/apple-touch-icon-152x152.png"><link rel="mask-icon" href="dist/img/icons/safari-pinned-tab.svg" color="#4DBA87"><meta name="msapplication-TileImage" content="dist/img/icons/msapplication-icon-144x144.png"><meta name="msapplication-TileColor" content="#000000"></head><body><noscript><strong>We're sorry but robot-framework doesn't work properly without JavaScript enabled. Please enable it to continue.</strong></noscript><div id="app"></div><script src="dist/js/chunk-vendors.6e0fb070.js"></script><script src="dist/js/app.604e1725.js"></script></body></html>
diff --git a/src/robocon-2024_sessions.json b/src/robocon-2024_sessions.json
@@ -1038,7 +1038,7 @@
     },
     "Track": null,
     "Abstract": "Ever had to restructure your project because it grew into an untameable monster? Or had to reorganise because more teams wanted to use your project? Or had to explain your tests to others? Or struggled how to setup a new RF project.\r\nOver the years we came up and fine-tuned an architecture that works from the very beginning to large scale projects.",
-    "Description": "We will take you along the ride during the course of seven years where we implemented Robot Framework in different environments at different clients. During this period, we ran into many challenges of which we are sure most of the attendees have already ran, or will run into sooner or later. \r\n\r\nOur journey started when our team responsible for test management in a large organisation decided Robot framework was the tool to help them to implement test automation within the organisation.\r\n\r\nAs so often in this situation, we started with one team that needed testcases for a web application. But, after a few months of success, problems start to occur with re-using parts of the scripts, maintainability and of course, the ever-expending universe of applications to test and the platforms they work on. Our solution? An architecture that puts keywords in segregated resource-files which is backed-up by straight forward and easy to apply rules that prevents ambiguous keywords and increases maintainability. \r\n\r\nBut a good architecture doesn\u2019t stop there. As our journey continuous, stakeholders want to get a grip on what is tested. The organization wants to use the framework across all the teams and use it for end-to-end testing of the most critical processes. Just a good technical architecture doesn\u2019t cut it here. Aggregation is needed and we needed to enhance the readability of the testscripts even further in order to enable collaboration between development teams and their stakeholders. We will tell you which additions to our architecture we came up with to answer these questions.\r\n\r\nOf course, as in every modern environment where software is created, pipelines and code repositories are supported and facilitated by the architecture, and we will briefly take a look at this as well.\r\n\r\nSince the first design of our architecture, we\u2019ve used this as a basis for several clients. As every environment comes with its own challenges, we found the basis of the architecture very reliable and with some tweaking here and there it never seems to let us down. So, join us for the ride and see if we can inspire you to face your own challenges with our architecture.",
+    "Description": "We will take you along the ride during the course of seven years where we implemented Robot Framework in different environments at different clients. During this period, we ran into many challenges of which we are sure most of the attendees have already ran, or will run into sooner or later.\r\n\r\nStarting with the troubles of re-using and maintaining scripts when we started to grow our test automation efforts. Then stakeholders wanted to get a grip on what is tested and we needed to get them easily involved. In the mean time more teams found themselves interfacing with systems from other teams and wanting to use the test automation of those teams for test setups and end-to-end testing as was requested by stakeholders.\r\n\r\nSince the first design of our architecture, we\u2019ve used this as a basis for several clients. Despite the fact that every environment comes with its own challenges, we found the basis of the architecture very reliable and with some tweaking here and there it never seems to let us down. So, join us for the ride and see if we can inspire you to face your own challenges with our architecture.",
     "Duration": 30,
     "Slot Count": 1,
     "Language": "en",
@@ -1096,7 +1096,7 @@
     },
     "Track": null,
     "Abstract": "How to organize your Robot Framework project? How to structure your test code in resource files? How to deal with very long lines? How to ...? Join this tutorial to learn where to find answers on these questions. We will also share a little secret how to become a contributor to the first Style Guide for Robot Framework.",
-    "Description": "Below is a preliminary outline of the Tutorial. Please note that it might be modified by the time Tutorial is held. This is in an effort to make the 2 hours as fruitful as possible.\r\n\r\n<br>\r\n\r\nTutorial will start with a general introduction, followed by a warm-up discussion in groups about the code quality, specifically, in the context of Robot Framework (~5+15 minutes minutes).\r\n\r\n<br>\r\n\r\nNext, tools and resources to assist code writing will be introduced: Style Guide, robocop, robotidy (~30 minutes)\r\n\r\n<br>\r\n\r\nOptional break (10 minutes)\r\n\r\n<br>\r\n\r\nAfter the break, guided hands-on sessions will be held. The first hands-on session will include an exercise to convert a messy Robot Framework code into a clean code with the help of the Style Guide, robocop and robotidy.\r\n(25 minutes)\r\n\r\n<br>\r\n\r\nReflection - opinions regarding the recommendations in the Style Guide, and default rules in the robocop/robotidy.\r\n(10 minutes)\r\n\r\n<br>\r\n\r\nThe last part of the tutorial will be dedicated to coming up with own conventions:\r\n- Configuring settings in robocop and robotidy (demo ~10 minutes)\r\n- Contributing to common Style Guide and using it as a common reference (~10 minutes).\r\n\r\n<br>\r\n\r\nConclusion (~5 minutes)\r\n\r\n<br>\r\n\r\nEveryone is welcome, from beginners to experts. We recommend participants to bring their own laptops for hands-on exercises but laptops are not mandatory for attending the tutorial.",
+    "Description": "Below is a preliminary outline of the Tutorial. Please note that it might be modified by the time Tutorial is held. This is in an effort to make the 2 hours as fruitful as possible.\r\n\r\n<br/>\r\n\r\nThe tutorial will start with a general introduction, followed by a warm-up discussion in groups about the code quality, specifically, in the context of Robot Framework (~5+15 minutes minutes).\r\n\r\n<br>\r\n\r\nNext, tools and resources to assist code writing will be introduced: Style Guide, robocop, robotidy (~30 minutes)\r\n\r\n<br>\r\n\r\nOptional break (10 minutes)\r\n\r\n<br>\r\n\r\nAfter the break, guided hands-on sessions will be held. The first hands-on session will include an exercise to convert a messy Robot Framework code into a clean code with the help of the Style Guide, robocop and robotidy.\r\n(25 minutes)\r\n\r\n<br>\r\n\r\nReflection - opinions regarding the recommendations in the Style Guide, and default rules in the robocop/robotidy.\r\n(10 minutes)\r\n\r\n<br>\r\n\r\nThe last part of the tutorial will be dedicated to coming up with own conventions:\r\n- Configuring settings in robocop and robotidy (demo ~10 minutes)\r\n- Contributing to common Style Guide and using it as a common reference (~10 minutes).\r\n\r\n<br>\r\n\r\nConclusion (~5 minutes)\r\n\r\n<br>",
     "Duration": 120,
     "Slot Count": 1,
     "Language": "en",
@@ -1116,7 +1116,7 @@
     },
     "Start": "2024-03-01T13:30:00+00:00",
     "End": "2024-03-01T17:30:00+02:00",
-    "Lessons Learned": "Participants will learn how not to write an ugly Robot Framework code. \r\n\r\n<br>\r\n\r\nThey will learn how well-written test code looks like, and what resources and tools they can use to help them write a clean Robot Framework code. Participants will also learn how they can contribute to defining the coding standard for Robot Framework.\r\n\r\n<br>\r\n\r\nFor more detailed outline of the proposed Tutorial, please refer to the \"Description\" filed in this application.",
+    "Lessons Learned": "<br>\r\n\r\nParticipants will learn \r\n- How well-written test code looks like.\r\n- What resources and tools they can use to help them write a clean Robot Framework code.\r\n- How they can contribute to defining the coding standard for Robot Framework.\r\n\r\n<br>",
     "Describe your intended audience": "Anyone interested is welcome to the Tutorial.",
     "Is this suitable for ..?": "Beginner RF user, Intermediate RF user, Advanced RF user"
   },