<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Devanshu Agrawal on Medium]]></title>
        <description><![CDATA[Stories by Devanshu Agrawal on Medium]]></description>
        <link>https://medium.com/@devanshuagrawal?source=rss-6b890a638e7b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Q-R3wJOruDKDQT-PAn6NaA.jpeg</url>
            <title>Stories by Devanshu Agrawal on Medium</title>
            <link>https://medium.com/@devanshuagrawal?source=rss-6b890a638e7b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:37:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@devanshuagrawal/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Jenkins and K6 don’t go together, until now]]></title>
            <link>https://medium.com/@devanshuagrawal/jenkins-and-k6-dont-go-together-until-now-d9c89227ae03?source=rss-6b890a638e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9c89227ae03</guid>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[groovy]]></category>
            <category><![CDATA[api-integration]]></category>
            <dc:creator><![CDATA[Devanshu Agrawal]]></dc:creator>
            <pubDate>Fri, 27 Apr 2018 22:03:28 GMT</pubDate>
            <atom:updated>2018-05-07T15:10:18.242Z</atom:updated>
            <content:encoded><![CDATA[<h4>We implemented a Groovy Script to run your K6 Tests on Jenkins so you dont have to</h4><h3>What is API Integration testing?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*xmrNcnEtKcBUHg6H." /></figure><p>The point of integration testing, as the name suggests, is to test <strong>whether many separately developed modules work together as expected</strong>. It was performed by activating many modules and running higher level tests against all of them to ensure they operated together. These modules could be parts of a single executable, or separate. In API Integration Testing, we run a bunch of api tests, linked to a specific service, together to monitor the expected responses. API Integration testing is a useful testing concept to uncover causal relationship between API changes and stability.</p><h3>Why do we use K6 and Jenkins?</h3><p>We started using <a href="https://k6.io/"><strong>K6</strong></a> so that we could confidently automate the API integration testing scripts and also perform load test. Given the plethora of features K6 platform offers along with integration with multiple visualization and DevOps tools, it seemed like a good choice to bet on.</p><p>However, K6 is still relatively new compared to other testing tool. There are some key integrations which the K6 Dev team is still building and often relies on contributions from the amazing Developer Community it has created.</p><p><a href="https://jenkins.io/"><strong>Jenkins</strong></a><strong> </strong>is an<a href="https://en.wikipedia.org/wiki/Open_source"> open source</a> automation server written in<a href="https://en.wikipedia.org/wiki/Java_%28programming_language%29"> Java</a>. Jenkins helps to automate the non-human part of the<a href="https://en.wikipedia.org/wiki/Software_development"> software development</a> process, with<a href="https://en.wikipedia.org/wiki/Continuous_integration"> continuous integration</a> and facilitating technical aspects of<a href="https://en.wikipedia.org/wiki/Continuous_delivery"> continuous delivery</a>. We use Jenkins, here specifically, to continuously run our tests without human interference to monitor API behaviour.</p><p>K6 does not output results in the JUnit XML required by Jenkins does to run tests and display them according to Jenkins metrics for continuous deployment. Hence, a groovy script is required to accept JSON results from K6 Tests, convert them into <a href="http://llg.cubic.org/docs/junit/"><strong>Jenkins understandable format (JUnit XML)</strong></a> and show metrics depending on the type of test and requirements.</p><h3>Writing the Groovy Script</h3><h4>Parsing K6 Results:</h4><p>When a test file is run on K6, it returns a JSON response stating the Type, Data, Values, Timestamp, Metrics etc expected from a Load Testing Tool. The JSON results are outputted as single lines for each metric or point. In order to parse this for our Groovy script, it is crucial to understand the <a href="https://docs.k6.io/docs/results-output"><strong>structure of the JSON results</strong></a>.</p><p>In our script, we use <a href="http://groovy-lang.org/json.html">JsonSlurper</a> to parse the JSON result line by line. We filtered out the metrics by Checks, but you can include as many metrics as you require. In our tests, we create a hierarchy of the groups which are then parsed along with the values of the checks and metrics.</p><p>We map the Groups to the objects TestSuite, TestClass, TestCase. The obtained data-model is outputted in the <a href="http://llg.cubic.org/docs/junit/">JUnit XML format</a>.</p><pre>// Sample Test Group Heirarchy<br>group(&quot;Inventory Tests&quot;, function () {</pre><pre> group(&quot;Category Tests&quot;, function () {</pre><pre>  group(&quot;Get all categories&quot;, function() {</pre><pre>    get_all_categories();</pre><pre>  });</pre><pre> });<br>});</pre><h3>Issues we encountered writing the script:</h3><h4>1. Particular implementation of groovy in pipelines:</h4><p>Once we started working on the script, we came across many issues which were particular to Jenkins and Groovy.</p><p>Generally, all objects that you create in a pipeline script must be serializable (the reason for this is that Jenkins must be able to serialize the state of the script so that it can be paused and stored on disk). We used the @NonCPS annotation since we have methods which use objects which aren’t serializable. When we put @NonCPS on a method, Jenkins will execute the entire method in one go without the ability to pause.</p><p>@TupleConstructor annotation provides the classical constructor with default properties. For example in object TestCase, it will create the constructor with first parameter as <strong>name</strong>, second parameter <strong>as classname</strong> etc. Constructor implementation depends upon the order of the variable declaration.</p><h4>2. No easy way to debug script:</h4><p>Due to Jenkins locked down groovy, we could only use one way of debugging the script which was to commit it on Bitbucket, then go to Jenkins Pipeline, Run it, and then find the errors from the logs. This was not only frustrating but also time consuming and we wished there was a shorter way.</p><h4>3. Cannot use 3rd party libraries:</h4><p>We found ourselves unable to use some of the third party libraries as it would not be accepted by Jenkins. Hence it became tricky to be creative with the script or implement it another way.</p><p><strong>k6JsonToJunitXml.groovy:</strong></p><pre><strong>import</strong> groovy.json.JsonSlurper<br><strong>import</strong> groovy.xml.*<br><strong>import</strong> groovy.transform.TupleConstructor<br><br><br><strong>def</strong> <strong>call(</strong>String inputFilePath<strong>,</strong> String outputFilePath<strong>){</strong><br>    process<strong>(</strong>inputFilePath<strong>,</strong> outputFilePath<strong>)</strong><br><strong>}</strong><br><br>@NonCPS<br><strong>def</strong> <strong>process(</strong>String inputFilePath<strong>,</strong> String outputFilePath<strong>)</strong> <strong>{</strong><br>    <br>    <strong>int</strong> totalTestsCount <strong>=</strong> 0<strong>,</strong> totalPassesCount <strong>=</strong> 0<strong>,</strong>    totalFailuresCount <strong>=</strong> 0<br><br>    <strong>def</strong> jsonSlurper <strong>=</strong> <strong>new</strong> JsonSlurper<strong>()</strong><br>    <strong>def</strong> testSuites <strong>=</strong> <strong>new</strong> HashSet<strong>&lt;</strong>TestSuite<strong>&gt;()</strong><br><br>    <strong>new</strong> <strong>File(</strong>inputFilePath<strong>).</strong>eachLine <strong>{</strong> line <strong>-&gt;</strong><br>        <em>// Read input file line by line</em><br>        <strong>def</strong> jsondata <strong>=</strong> jsonSlurper<strong>.</strong>parse<strong>(</strong>line<strong>.</strong>toCharArray<strong>());</strong><br>        <strong>if</strong> <strong>(</strong>jsondata<strong>.</strong>metric <strong>==</strong> &quot;checks&quot; <strong>&amp;&amp;</strong> jsondata<strong>.</strong>data<strong>.</strong>tags<strong>)</strong> <strong>{</strong><br>            <br>            <strong>def</strong> data <strong>=</strong> jsondata<strong>.</strong>data<br>            EntityNames entityNames <strong>=</strong> nameSplitter<strong>(</strong>data<strong>)</strong><br><br>            <strong>def</strong> status <strong>=</strong> getStatus<strong>(</strong>data<strong>)</strong><br>            <strong>def</strong> checkName <strong>=</strong> assertName<strong>(</strong>data<strong>)</strong><br><br>            <em>//creating Testsuites here</em><br>            <strong>def</strong> parsedTestSuite <strong>=</strong> <strong>new</strong>  TestSuite<strong>(</strong>entityNames<strong>.</strong>testSuiteName<strong>)</strong><br><br>            <em>//creating Testcases here</em><br>            <strong>def</strong> parsedTestCase <strong>=</strong> <strong>new</strong> TestCase<strong>(</strong>entityNames<strong>.</strong>testCaseName<strong>,</strong> entityNames<strong>.</strong>testClassName<strong>,</strong> status<strong>)</strong><br><br>            <strong>def</strong> testSuite <strong>=</strong> testSuites<strong>.</strong>find <strong>{</strong> it<strong>.</strong>equals<strong>(</strong>parsedTestSuite<strong>)</strong> <strong>}</strong><br>            <strong>if</strong> <strong>(!</strong>testSuite<strong>)</strong> <strong>{</strong><br>                testSuite <strong>=</strong> parsedTestSuite<br>                testSuites<strong>.</strong>add<strong>(</strong>testSuite<strong>)</strong><br>            <strong>}</strong><br><br>            <strong>def</strong> testCase <strong>=</strong> testSuite<strong>.</strong>testCases<strong>.</strong>find <strong>{</strong> it<strong>.</strong>equals<strong>(</strong>parsedTestCase<strong>)</strong> <strong>}</strong><br>            <strong>if</strong> <strong>(!</strong>testCase<strong>)</strong> <strong>{</strong><br>                testCase <strong>=</strong> parsedTestCase<br>                testSuite<strong>.</strong>testCases<strong>.</strong>add<strong>(</strong>testCase<strong>)</strong><br>                testSuite<strong>.</strong>testCount<strong>++</strong><br>            <strong>}</strong><br><br>            <strong>if</strong> <strong>(</strong>status <strong>==</strong> &quot;failed&quot;<strong>)</strong> <strong>{</strong><br>                testCase<strong>.</strong>failures<strong>.</strong>add<strong>(</strong>checkName<strong>)</strong><br>                testSuite<strong>.</strong>failuresCount<strong>++</strong><br>                totalFailuresCount<strong>++</strong><br>            <strong>}</strong> <strong>else</strong> <strong>{</strong><br>                totalPassesCount<strong>++</strong><br>            <strong>}</strong><br><br>            testCase<strong>.</strong>assertions<strong>++</strong><br>        <strong>}</strong><br>    <strong>}</strong><br>    printXml<strong>(</strong>testSuites<strong>,</strong> outputFilePath<strong>)</strong><br><strong>}</strong><br><br>@NonCPS<br><strong>def</strong> <strong>printXml(</strong>testSuites<strong>,</strong> outputFilePath<strong>){</strong><br>    <strong>def</strong> builder <strong>=</strong> <strong>new</strong> StreamingMarkupBuilder<strong>()</strong><br>    builder<strong>.</strong>encoding <strong>=</strong> &#39;UTF-8&#39;<br><br>    <strong>def</strong> testsuitesPrint <strong>=</strong> builder<strong>.</strong>bind <strong>{</strong><br>        delegate<strong>.</strong>testsuites<strong>()</strong> <strong>{</strong><br>            <strong>for</strong> <strong>(</strong>TestSuite testSuite <strong>:</strong> testSuites<strong>)</strong> <strong>{</strong><br>                delegate<strong>.</strong>testsuite<strong>(</strong>name: testSuite<strong>.</strong>name<strong>,</strong> tests: testSuite<strong>.</strong>testCount<strong>,</strong> failures: testSuite<strong>.</strong>failuresCount<strong>)</strong> <strong>{</strong><br>                    <strong>for</strong> <strong>(</strong>TestCase testCase <strong>:</strong> testSuite<strong>.</strong>testCases<strong>)</strong> <strong>{</strong><br>                        delegate<strong>.</strong>testcase<strong>(</strong>name: testCase<strong>.</strong>name<strong>,</strong> assertions: testCase<strong>.</strong>assertions<strong>,</strong> classname: testCase<strong>.</strong>classname<strong>,</strong> status: testCase<strong>.</strong>status<strong>)</strong> <strong>{</strong><br>                            <strong>for</strong> <strong>(</strong>String message <strong>:</strong> testCase<strong>.</strong>failures<strong>)</strong> <strong>{</strong><br>                                delegate<strong>.</strong>failure<strong>(</strong>message: message<strong>,</strong> type: &quot;Check failed&quot;<strong>)</strong><br>                            <strong>}</strong><br>                        <strong>}</strong><br>                    <strong>}</strong><br>                <strong>}</strong><br>            <strong>}</strong><br>        <strong>}</strong><br>    <strong>}</strong><br><br><br>    <strong>def</strong> outputFile <strong>=</strong> <strong>new</strong> File<strong>(</strong>outputFilePath<strong>).</strong>newWriter<strong>()</strong><br>    outputFile <strong>&lt;&lt;</strong> XmlUtil<strong>.</strong>serialize<strong>(</strong>testsuitesPrint<strong>)</strong><br>    outputFile<strong>.</strong>close<strong>()</strong><br><strong>}</strong><br><br>@NonCPS<br><strong>def</strong> <strong>nameSplitter(</strong>stringInput<strong>)</strong> <strong>{</strong><br>    String<strong>[]</strong> parsedNames <strong>=</strong> stringInput<strong>.</strong>tags<strong>.</strong>group<strong>.</strong>split<strong>(</strong>&quot;::&quot;<strong>)</strong><br>    parsedNames <strong>=</strong> parsedNames<strong>.</strong>drop<strong>(</strong>1<strong>)</strong><br>    <strong>def</strong> size <strong>=</strong> parsedNames<strong>.</strong>size<strong>()</strong><br><br>    <em>//Assign the index values of parsedName array to definite entities- testSuiteName, testClassName, testCaseName based on array size</em><br>    EntityNames result <strong>=</strong> <strong>new</strong> EntityNames<strong>(</strong>&quot;&quot;<strong>,</strong> &quot;&quot;<strong>,</strong> &quot;&quot;<strong>)</strong><br>    <strong>if</strong> <strong>(</strong>size <strong>==</strong> 1<strong>)</strong> <strong>{</strong><br>        result<strong>.</strong>testSuiteName <strong>=</strong> parsedNames<strong>[</strong>0<strong>]</strong><br>        result<strong>.</strong>testClassName <strong>=</strong> parsedNames<strong>[</strong>0<strong>]</strong><br>        result<strong>.</strong>testCaseName <strong>=</strong> parsedNames<strong>[</strong>0<strong>]</strong><br>    <strong>}</strong> <strong>else</strong> <strong>if</strong> <strong>(</strong>size <strong>==</strong> 2<strong>)</strong> <strong>{</strong><br>        result<strong>.</strong>testSuiteName <strong>=</strong> parsedNames<strong>[</strong>0<strong>]</strong><br>        result<strong>.</strong>testClassName <strong>=</strong> parsedNames<strong>[</strong>1<strong>]</strong><br>        result<strong>.</strong>testCaseName <strong>=</strong> parsedNames<strong>[</strong>1<strong>]</strong><br>    <strong>}</strong> <strong>else</strong> <strong>if</strong> <strong>(</strong>size <strong>&gt;</strong> 2<strong>)</strong> <strong>{</strong><br>        StringBuffer testCaseName <strong>=</strong> <strong>new</strong> StringBuffer<strong>()</strong><br>        <strong>for</strong> <strong>(</strong>i <strong>=</strong> 2<strong>;</strong> i <strong>&lt;</strong> size<strong>;</strong> i<strong>++)</strong> <strong>{</strong><br>            testCaseName<strong>.</strong>append<strong>(</strong>parsedNames<strong>[</strong>i<strong>])</strong><br>        <strong>}</strong><br>        result<strong>.</strong>testSuiteName <strong>=</strong> parsedNames<strong>[</strong>0<strong>]</strong><br>        result<strong>.</strong>testClassName <strong>=</strong> parsedNames<strong>[</strong>1<strong>]</strong><br>        result<strong>.</strong>testCaseName <strong>=</strong> testCaseName<strong>.</strong>toString<strong>()</strong><br>    <strong>}</strong><br>    <strong>return</strong> result<br><strong>}</strong><br><br>@NonCPS<br><strong>def</strong> <strong>assertName(</strong>stringInput<strong>)</strong> <strong>{</strong><br>    <strong>def</strong> checkname <strong>=</strong> stringInput<strong>.</strong>tags<strong>.</strong>check<br>    <strong>return</strong> checkname<br><strong>}</strong><br><br>@NonCPS<br><strong>def</strong> <strong>getStatus(</strong>data<strong>)</strong> <strong>{</strong><br>    String value <strong>=</strong> data<strong>.</strong>value<br>    <strong>if</strong> <strong>(</strong>value <strong>==</strong> &quot;1&quot;<strong>)</strong> <strong>{</strong><br>        <strong>return</strong> &quot;passed&quot;<strong>;</strong><br>    <strong>}</strong><br>    <strong>if</strong> <strong>(</strong>value <strong>==</strong> &quot;0&quot;<strong>)</strong> <strong>{</strong><br>        <strong>return</strong> &quot;failed&quot;<strong>;</strong><br>    <strong>}</strong><br><strong>}</strong><br><br>@TupleConstructor<strong>()</strong><br><strong>public</strong> <strong>class</strong> <strong>EntityNames</strong> <strong>{</strong><br>    String testSuiteName<br>    String testClassName<br>    String testCaseName<br><strong>}</strong><br><br>@TupleConstructor<strong>(</strong>includes <strong>=</strong> <strong>[</strong>&quot;name&quot;<strong>])</strong><br><strong>public</strong> <strong>class</strong> <strong>TestSuite</strong> <strong>{</strong><br>    String name<br>    <strong>int</strong> failuresCount<br>    <strong>int</strong> testCount <strong>=</strong> 0<br>    <strong>def</strong> testCases <strong>=</strong> <strong>new</strong> HashSet<strong>&lt;</strong>TestCase<strong>&gt;()</strong><br><br>    @Override<br>    @NonCPS<br>    <strong>public</strong> <strong>boolean</strong> <strong>equals(</strong>Object o<strong>)</strong> <strong>{</strong><br><br>        TestSuite ts <strong>=</strong> <strong>(</strong>TestSuite<strong>)</strong> o<strong>;</strong><br>        <strong>return</strong> Objects<strong>.</strong>equals<strong>(</strong>name<strong>,</strong> ts<strong>.</strong>name<strong>);</strong><br>    <strong>}</strong><br><br>    @Override<br>    @NonCPS<br>    <strong>public</strong> <strong>int</strong> <strong>hashCode()</strong> <strong>{</strong><br>        <strong>return</strong> Objects<strong>.</strong>hash<strong>(</strong>name<strong>);</strong><br>    <strong>}</strong><br><strong>}</strong><br><br>@TupleConstructor<strong>(</strong>includes <strong>=</strong> <strong>[</strong>&quot;name&quot;<strong>,</strong> &quot;classname&quot;<strong>,</strong> &quot;status&quot;<strong>])</strong><br><strong>public</strong> <strong>class</strong> <strong>TestCase</strong> <strong>{</strong><br>    String name<br>    String classname<br>    String status<br>    <strong>int</strong> assertions<br>    <strong>def</strong> failures <strong>=</strong> <strong>[]</strong><br><br>    @Override<br>    @NonCPS<br>    <strong>public</strong> <strong>boolean</strong> <strong>equals(</strong>Object o<strong>)</strong> <strong>{</strong><br><br>        TestCase tc <strong>=</strong> <strong>(</strong>TestCase<strong>)</strong> o<strong>;</strong><br>        <strong>return</strong> Objects<strong>.</strong>equals<strong>(</strong>name<strong>,</strong> tc<strong>.</strong>name<strong>)</strong> <strong>&amp;&amp;</strong> Objects<strong>.</strong>equals<strong>(</strong>classname<strong>,</strong> tc<strong>.</strong>classname<strong>);</strong><br>    <strong>}</strong><br><br>    @Override<br>    @NonCPS<br>    <strong>public</strong> <strong>int</strong> <strong>hashCode()</strong> <strong>{</strong><br>        <strong>return</strong> Objects<strong>.</strong>hash<strong>(</strong>name<strong>,</strong> classname<strong>);</strong><br>    <strong>}</strong><br><strong>}</strong></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/0*Gg3_2ylVKorwWLI8." /><figcaption><a href="http://testingology.com/">http://testingology.com</a></figcaption></figure><p>We decided to share the script with the community so that the developers can save time by not indulging themselves into hard labor only to find out the support for their implementation doesn’t exist. Hence, anyone who plans to use K6 for their load/integration testing along with Jenkins for test automation, can use and edit the groovy script to display the type of metrics according to requirements without hassle and save time.</p><h4>Using the Script</h4><p>Pipeline has <a href="https://jenkins.io/doc/book/pipeline/shared-libraries/"><strong>support</strong></a> for creating “Shared Libraries” which can be defined in external source control repositories and loaded into existing Pipelines.</p><p>The script can be added in the pipeline as a step after the tests have been run to convert the json result file into junit xml.</p><pre>//K6 has to be run using this parameter<br>&quot;out json=&lt;test_result.json&gt;”</pre><p>The scripts can be imported as a Library and can be called like this:</p><pre>@Library(&#39;jenkins-repository&#39;) _<br>node {<br>    stage(&quot;Checkout&quot;) {<br>        ...<br>        checkout scm <br>    }<br>    stage (&quot;Run Test&quot;) {<br>        ...k6 run --out json=results.json src/integration_tests/integration.js ...           k6JsonToJunitXml(&quot;results.json&quot;, &quot;output.xml&quot;)</pre><pre>...<br>    stage (&quot;Reports&quot;){<br>        ...<br>    }<br>}</pre><p>The script can also be used for different types of tests besides API Integration Tests and can be customized to output different types of metrics or even add metrics which are currently not provided by K6. The options are limitless!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0TOw651VRjS6eiJgjqzm5w.png" /><figcaption>Jenkins test result analyzer</figcaption></figure><h3>Conclusion</h3><p>We use integration and load testing as a development process, in a way that will clear any issues a user might face in real world when a bunch of applications run alongside each other to serve the customer. For this, we can choose from multiple options both for testing framework and to automate this process. In case, a dev team decides to go with the advantages of K6 and Jenkins like we did, they are free to use<strong> </strong><a href="https://github.com/devns98/K6-to-JUnit-XML-Jenkins"><strong>this Groovy script</strong></a><strong> </strong>to expedite their testing process and not get into the nitty-gritty of Jenkins and Groovy.</p><p>I created this script while interning at <a href="https://www.chefhero.com/"><strong>ChefHero</strong></a>. Special shout-out to K6 Admins for being so helpful!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9c89227ae03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Samsung Galaxy S9: A Very Smart Upgrade]]></title>
            <link>https://medium.com/totally-biased-thoughts-and-reviews/the-samsung-galaxy-s9-a-very-smart-upgrade-c173218bca4c?source=rss-6b890a638e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c173218bca4c</guid>
            <category><![CDATA[mobile-world-congress]]></category>
            <category><![CDATA[smartphones]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[samsung]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Devanshu Agrawal]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 15:43:56 GMT</pubDate>
            <atom:updated>2018-02-26T23:37:31.092Z</atom:updated>
            <content:encoded><![CDATA[<p>Its funny how we wait for an event for months, anticipating the newest flagships, knowing all the expected features, reviewing all the ‘leaks’ beforehand and still getting excited when the actual device launches. Well, that is exactly what happened with the all new Samsung Galaxy S9 and S9 Plus when it was launched at the Unpacked event at MWC Barcelona. Many would be glad Samsung listened to the customer feedback and re-iterated their vision for the galaxy line up. They did not jump into a fancy half-done feature just to stay ahead of the trend, but instead improved their already amazing product and the features they excel in. Lets see what all has changed from the S8 to S9:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FFI2CpNdaJAc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DFI2CpNdaJAc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FFI2CpNdaJAc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/351a9298b43680560d5f4489e721f766/href">https://medium.com/media/351a9298b43680560d5f4489e721f766/href</a></iframe><h3>The Obvious Upgrades:</h3><ol><li>The new Exynos 9810 chipset powers the smartphone (unless you’re in the US, where you get Qualcomm’s Snapdragon 845) coupled with 6gb of ram to accomplish the heavy tasks.</li><li>Google’s updated software in the shape of Android Oreo takes control of the sweet Android experience of the phone with TouchWiz on top.</li><li>The S9 also trims a bit of the already almost-bezel-less but gorgeous QHD+ Super AMOLED 18.5:9 Infinity Display, adding a few millimeters of thickness to house the components.</li><li>The IRIS scanner makes a return to add additional security alongside the presence of a more accessible fingerprint scanner housed under the camera module.</li><li>The headphone jack makes a return too. Its 2018. I have to mention this.</li><li>The external storage support has also been increased to 400 gigabytes. Extra storage is always appreciated, props to Samsung for the nice touch.</li><li>The new line-up also brings in a couple of new colors to existing glass back design. Lilac Purple anyone?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OIHLMv5O9y6Yh36JNyJPvQ.jpeg" /><figcaption>Credits: techradar.com</figcaption></figure><h3>The Main Attractions:</h3><ol><li>Surround Speakers. YES. Glad Samsung is taking an initiative and getting inspired from the success of Google Pixel line-up to introduce surround sound to their existing speakers. The earpiece speaker and the bottom-firing speaker, tuned by AKG Acoustics, work together to dish out amazing sound quality.</li><li>Camera Re-Imagined. The promise made by this tagline does seem to be true on paper. Samsung’s dual-aperture technology allows the camera aperture to expand and contract depending on light levels, just as the human eye does. In short, the camera reduces over-exposed pictures and improves low light images based on the situation. The additional camera also adds on the feature of ultra slo-mo at 960 fps which triggers itself based on movement, which is amazing and new for the smartphone space.</li><li>Bixby Vision and AR-Emoji. Mild reactions to this one but nonetheless a nice addition to Samsung’s answer to both Google and Apple. The execution behind AR-Emoji is half-baked, but is promising if improved by software updates. Bixby Vision is good execution, but is limited and highly doubtful if it will be used enough. Samsung doesn&#39;t want to fall back on any features which customers of other companies enjoy. So this is a step in good direction.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_wWbEd5LxZq6BK4hEd1kw.jpeg" /><figcaption>Photo Credits: <a href="https://www.theverge.com/users/James%20Bareham"><em>James Bareham</em></a><em> (verge.com)</em></figcaption></figure><h3>To Buy Or Not To Buy?</h3><p>Definitely a buy if you are in the market for a new high-end smartphone, with modern glass design, a redesigned camera for all your needs, as well as a few tricks up its sleeve. If you already have a high end smartphone from the Big 5, then there is no need to upgrade. Given the price difference and feature set between the S9, S9+ and the already great S8, one would might as well go for the Plus in that segment which held the focus (pun intended) during the launch.</p><p>The S9 gives a promising start to 2018 which seems like the year to polish the existing flagships starting with the LG V30s and the Samsung S9 (probably followed by Apple Iphone X Plus too). Let me know what you think about the latest from Samsung in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c173218bca4c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/totally-biased-thoughts-and-reviews/the-samsung-galaxy-s9-a-very-smart-upgrade-c173218bca4c">The Samsung Galaxy S9: A Very Smart Upgrade</a> was originally published in <a href="https://medium.com/totally-biased-thoughts-and-reviews">Totally Biased Thoughts And Reviews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nailing the on-boarding experience]]></title>
            <link>https://medium.com/uwaterloo-voice/nailing-the-on-boarding-experience-8119b21d8a3?source=rss-6b890a638e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8119b21d8a3</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[talent-management]]></category>
            <category><![CDATA[recruiters]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Devanshu Agrawal]]></dc:creator>
            <pubDate>Wed, 17 Jan 2018 15:54:44 GMT</pubDate>
            <atom:updated>2019-02-13T05:07:12.197Z</atom:updated>
            <content:encoded><![CDATA[<p>The intern season is upon us and as the students get prepping for interviews, so do the recruiters and companies. One might wonder how much effort goes into planning the on-boarding part of an internship, laying the foundation of what the company does and how it can benefit both the parties. I feel like the on-boarding process of <a href="https://chefhero.com/">ChefHero</a>, where I currently am interning, is worth commending and I hope other startups/companies get inspired from them. <strong>There is a tl;dr in the end for the busy bees.</strong></p><p>Now the interesting part is, this was the company’s first attempt at an official on-boarding process. As a startup which is expanding rapidly, they realized that there is a need for an official on-boarding for new hires. In this post, I will focus on how they executed their on-boarding program and brought the interns and new hires up to speed. The introduction and training events/meetings were sandwiched in the first regular working week and included developers, VP’s of different teams, product managers, sales team, operations team, customer success team and sessions with the CEO himself. As you can guess, it gave us a chance to get to know most of the people, their day to day tasks, the multiple products as well as the company’s vision and values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8pCsVbHmOaAXnFa03YQzQ.png" /><figcaption>Schedule for the week</figcaption></figure><h3>The On-Boarding Week</h3><p><strong>Monday:</strong></p><p>Our day started with a warm welcome from the VP of Product, Kim who took us through the journey of ChefHero and introduced us to the product and vision of the company and what they are targeting. We had already been working three days before the on-boarding so it was easy to grasp. From here on started our stream of questions who she very patiently answered. Trust me, there were many.</p><p>We were given a bunch of tasks by our direct manager and VP of Engineering, Oliver . Soon after followed a meeting with Oliver to discuss the engineering department overview where we learned about the stack and processes the engineering team follows and his expectations from both of us interns.</p><p>Soon after followed a meeting with Craig, VP of Growth, who introduced himself, shed light on his impressive background and then instilled the growth plan he and his team have for the upcoming future. I bombarded him with questions to which he gave very convincing and promising answers.</p><p>We ate up some time from our next meeting with Saif, CEO, where we learned about the vision and culture of ChefHero from his perspective. The story behind how the company started was compelling, in a way where we wondered how he set up a company in such a short time. He laid out his experience, pivots and roadblocks which he and his CTO, Diego, had to overcome to be where they are today. With the amount of knowledge we had gathered, we needed a break and then got back to work looking forward to the next day with less whites than blue on our schedule.</p><p><strong>Tuesday:</strong></p><p>This was the day it felt like we were back at the university. The day started with coffee, Kim, and Oliver who took us through an introduction to Product and Engineering. Since both the teams work together, it gave us a good insight to the processes and work flow established by both of them.</p><p>The meeting ended with us running for the next one with Melanie, Product Manager. She walked us through her very interesting background and then gave us an insight on the company’s main clients. We realized we had underestimated the company’s potential client base till now.</p><p>After lunch, we gathered around Jonathan, Product Manager, who walked us through the main portal and the apps. This was a hands-on activity and was well executed. We left the room knowing a lot more about the product and where it needs some work done. This was much needed as we would have spent a lot of time figuring out the products otherwise.</p><p>Our last meeting for today was with Kim again, who talked about one of my favourite topics in a business, the Competition. We spoke about the competitive landscape and how the company plans to tackle the competitors.</p><p><strong>Wednesday:</strong></p><p>We got more work done on Wednesday as we had only two main meetings. The first one was with the VP of Operations, who introduced the operations team and their tasks to us. What followed was more of a discussion about the company and how the team works in conjunction with other teams.</p><p>The next meeting was with Mel and Kim where they spoke about the company’s clients in detail. We were given an insight on the different types of clients and their expectations from the company. As a company which believes in putting all their efforts in making sure the customer is satisfied, this session was very important in putting things in perspective.</p><p><strong>Thursday:</strong></p><p>One of the company’s ritual is to take an early morning trip with the CEO to the Ontario Food Terminal where we can experience the humble beginnings as well as the massive scale of the industry in one visual. The wall of docking bays filled to capacity and trucks waiting to deliver the food which feeds the region of Ontario, one great visual.</p><p>The day didn&#39;t end there as we had a session with Craig who gave us an intro to the sales team and how it functions in a startup environment. He walked us through the challenges and how they overcome the huge task of increasing the sales of the company. What started with cold calling became a proper process is very intriguing to me.</p><p>Immediately after, we had a meeting with Liam to discuss Vendor relations. Vendors are the second half of the company’s clients and maintaining a healthy relationship with huge vendors can be a great task. Morin and his team showed us how they take on this huge task.</p><p>We concluded the day’s meetings with a Lunch and Learn with the design team, Marshall and Bianca. They gave us a very interesting take on design processes and how to make the product visually and pragmatically appealing. We had a one-on-one session with them on our first day to get a sense of the design and also for them to get feedback from fresh eyes.</p><p><strong>Friday:</strong></p><p>We have almost reached the end of the on-boarding process. We started the day with an intro session by Zein and Vanessa from the customer support team. ChefHero goes above and beyond to keep the customers happy, and its the CS team which achieves this amazing feat. We completed a session full of knowledge about the various softwares used by the team as well as processes and methods being put in place as they expand.</p><p>We completed a sprint meeting with the entire dev team after that while having a few drinks in the board room and then relaxing with board games and cheers all around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*MgQDfBZ1xsg2bEyU5l20ug.png" /></figure><h3>Tl;dr:</h3><p>The on-boarding week was full of events and sessions with different teams to get an overview of what the company is about. The sessions were crafted in a way that the new hires would be brought up to speed as the rest of the team. By investing in a week full of sessions, they had saved a lot of hours of confusion and ambiguity to increase the productivity of the new hires for the following months.</p><h3>Conclusion:</h3><p>The main purpose of this article is to state the importance of a proper on-boarding process which will benefit the company and employees in the long run. I found out that this on-boarding process is still lacking in various companies and startups. Some might argue that this will take away a lot of man hours and slow down processes and development. But by establishing a system, the company makes the new hires feel valued and that pays off eventually. The pros definitely outweigh the cons in investing in proper on-boarding.</p><p>“When people are financially invested, they want a return. When people are emotionally invested, they want to contribute.” — <em>Simon Sinek</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8119b21d8a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uwaterloo-voice/nailing-the-on-boarding-experience-8119b21d8a3">Nailing the on-boarding experience</a> was originally published in <a href="https://medium.com/uwaterloo-voice">uWaterloo Voice</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>