<?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 Anirudh Prayaga on Medium]]></title>
        <description><![CDATA[Stories by Anirudh Prayaga on Medium]]></description>
        <link>https://medium.com/@anirudh114-prayaga?source=rss-b0630a5ff9f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*07MKR26jxD4sfpqQRjH2Pw.jpeg</url>
            <title>Stories by Anirudh Prayaga on Medium</title>
            <link>https://medium.com/@anirudh114-prayaga?source=rss-b0630a5ff9f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:00:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anirudh114-prayaga/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[Trip to the Great Smoky Mountains — Summer 2021]]></title>
            <link>https://anirudh114-prayaga.medium.com/trip-to-the-great-smoky-mountains-summer-2021-2875901454c?source=rss-b0630a5ff9f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2875901454c</guid>
            <category><![CDATA[gatlinburg]]></category>
            <category><![CDATA[nashville]]></category>
            <category><![CDATA[laurel-falls]]></category>
            <category><![CDATA[ober-gatlinburg]]></category>
            <category><![CDATA[smoky-mountains]]></category>
            <dc:creator><![CDATA[Anirudh Prayaga]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 01:03:07 GMT</pubDate>
            <atom:updated>2021-07-06T01:03:07.482Z</atom:updated>
            <content:encoded><![CDATA[<p>After a lot of planning and forethought on where to go for the July 4th weekend, we zeroed in on the Most visited national park of the US — <strong>Great Smoky Mountains National Park.</strong></p><p>We had started from Des Moines, IA and reached Nashville, TN on July 1st night. Then had taken the rental car from the BNA airport to drive around ~3 hours to Knoxville. Surprisingly, the AVIS rental car counter in the airport was pretty empty and we were the only customers there even though the rental car industry has been pretty busy due to the post COVID travel rush in the recent times.</p><p>On that good note we started to Knoxville, TN which is approximately an hour away from the national park. We reached the hotel fairly tired and rested for the night excited about the ziplining that we were gonna do the next day.</p><h3>Day 1 — July 2nd</h3><p>We started to the <a href="https://www.climbworks.com/smoky_mountains/">CLIMB Works</a> site where we will be doing the ziplining. Our reservation for the party of 4 was at 1 pm and we were told to be there 40 mins before for the check-in procedures and related stuff. We were lucky to get the reservation just couple days before our actual date of ziplining, but would recommend booking at least 1 week in advance checking the weather.</p><p>After wearing the zipline gear (which includes a water bottle), we were driven in an ATV to the top of the mountain where there was a ziplining tree platform. We were all excited about this!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eSy2wv70dGIW-lMNM59Xbg@2x.jpeg" /><figcaption>Getting ready for the zipline</figcaption></figure><p>Our tour guides were Mik, Raine and Megan and all three were very knowledgeable and super funny. They gave us some great tips and did some amazing tricks on the ziplines and encouraged everyone to do those. It is a 6 course zip line with varying length, height and speed for each one. There will be other people in the party as well and there are two parallel lines to zip. The views of the mountains were amazing !!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0ZWfeadFfh-H_J8I2lIng@2x.jpeg" /><figcaption>Raine, Mik doing a trick and Megan clicking a picture.</figcaption></figure><p>At each point the tour guides Mik and Raine gave us a brief history of that point and the mountains nearby in particular. Megan took pictures of all of us at various spots in the ziplines all along the tour and those were up for purchase at the check out. All in all it took around 2.5 hours from check in to check out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GT0QsxSvSgklTbO3JV4gzQ@2x.jpeg" /><figcaption>One with our tour guides</figcaption></figure><p>We then went to Gatlinburg very famished. We drove around the town to explore what was there and it was very very busy and had a great vibe to it with tons of activities, parking lots and food options that were available. Best way to explore the town is to walk by foot.</p><p>There is ‘Marathon’ gas station at the end of the Gatlinburg town on US-441 S and right beside it was ‘Cici’s’ pizza which is a pizza buffet restaurant. We went in there and tried their soup, pasta, breadsticks, pizza and deserts. Highly recommend that restaurant and you have a very decent parking space for customers, so you don’t need to worry about it, which is a bonus in Gatlinburg.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aP02RWYifRRH0wYCqPpS3Q@2x.jpeg" /></figure><p>After that we entered the Great Smoky Mountain National Park near the North Entrance turnaround and took some good pictures. There is a limited parking space where you can park the vehicle for a few minutes, take a picture of the national park board sign and explore the trail along side a beautiful creek.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2eE3bAhFNdfCfZVph4jcw@2x.jpeg" /><figcaption>A serene creek by the Gatlinburg trail</figcaption></figure><p>After contemplating to hike to ‘Grotto falls’ and ‘Baskin creek’ falls we ended up hiking to the ‘Laurel Falls’. If you are a fan of waterfalls, you will definitely love the Smokies as there are many many waterfalls in the park with amazing views.</p><p>Once we were at the Laurel falls trail parking, a rumor was going around that there was a Mama black bear along with her two cubs that was spotted on the trail. We were asking few people about this and indeed one young lady spotted the cubs but not the mama bear. We were little bit nervous and bit excited about the potential wildlife encounter. Nevertheless, we carried on with our hike to the Laurel falls. It was a 1.3 mile round trip hike with great views of the valleys and it was lush green everywhere in between.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WWCQlFTThRFSVENA_k5cKw@2x.jpeg" /><figcaption>Laurel Falls</figcaption></figure><p>It was almost sunset time by the time we came back to the Laurel falls trail parking lot and we were headed to explore Pigeon forge town. It’s a big brother of Gatlinburg with a lot more food joints, activities, gift shops, ATV rentals etc. present there. If you are a fan of fast-food, this is the place to grab a bite while you are in the Smokies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KPTNQM88F007fcfkT45TaA@2x.jpeg" /><figcaption>A tree in Pigeon Forge main street</figcaption></figure><h3><strong>Day 2 — July 3rd</strong></h3><p>Day 1 was a long day for us and we had relaxed at the hotel for a little longer on day 2’s morning. So we had a rather late start to the day after having our brunch. We had so many trails in our minds to explore but were unable to decide on what to do among the cataract falls, mingo falls or the arch rock . As we had already been to a waterfall on day 1, we decided to go to ‘Arch rock’.</p><p>We continued to drive into the woods along the US- 441 S and parked at the ‘Alum Cave bluff trail&#39; head’s parking lot. There was access to ‘west prong little pigeon river’ at the entrance of the trail which was beautiful. There were numerous small wooden bridges all along the trail including near the entrance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y4dADgPVMKaIAlv5LuNgtg@2x.jpeg" /></figure><p>This was the best trail we’ve taken in the Smokies. The terrain was little rough and steep but the ‘Alum cave trail’ had so many wonderful spots where the ‘Alum cave creek’ was just gorgeous. The sound of water flowing, cutting through the rocks on it’s path is still reverberating in my ears! No wonder there were so many people that were taking this trail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rzoGodeHLD1AFUEOYES_UQ@2x.jpeg" /></figure><p>This trail till the arch rock was 1.3 miles one way. The terrain was not challenging till the 1 mile mark but after that it got steep and rocky. To cross the ‘Styx branch’ of the ‘Alum cave creek’ there were few bridges that were carved directly from the trunk of a tree. These were very beautiful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KD0V8uvZH3pHrtLUFwuJlg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fv5QVxJf_1CMtJB8IapLsQ@2x.jpeg" /></figure><p>The bridge shown above is so narrow that we can maintain just a single file. From this point it was just 0.3 mile to the ‘Arch rock’. We were planning to end our hike at ‘Arch Rock’, but there were some people who were continuing there hike till Mt. Le Conte which was 5 miles from the trail head&#39;s parking lot. Carry lots of water on this trail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*Z4Ck3Yq1EbjoaYuVwKgy7g@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uE1Ye03WIFxg4eMi8tTpZg@2x.jpeg" /></figure><p>It was a very satisfying hike. After finishing this trail and getting some gatorade and water from our car, we then drove along south US 441 and took a right turn on the Clingman’s Dome road to the most famous ‘<em>Clingman’s Dome</em>’ to take a 360 degree look at the Smokies. This is technically in North Carolina State. Parking is very tricky here but as we were there almost at the end of the day(around 6 pm) , we were able to find some parking. There is a 0.5 mile paved trail to the top of the ‘Clingman’s Dome’ which is a little bit steep but not very challenging. It is well worth it as the views from the dome are spectacular and you can take a 360 degree look at the beautiful Smokies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VawMuO2pAqDHC-CTNWKfxw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aklStjfA9Zqy4M0gbDNKkg@2x.jpeg" /></figure><p>Right beside the ‘Clingman’s Dome’ trail, there was ‘Appalachian trail’ which was covered in canopy along with lot of fern trees and we were lucky enough to spot a deer in that trail! We were then headed to ‘Newfound gap’ right at the border of North Carolina and Tennessee. After exploring the area and witnessing some great views, we called it a day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OTyFvXXAPYrDwjQxZH-dJA@2x.jpeg" /></figure><p><strong>Day 3 — July 4th</strong></p><p>This was the last day and short day for us as we had to travel around ~3.5 hours from Gatlinburg back to Nashville to take our flight to Des Moines. We wanted to plan well and keep the day short so that we won’t be late for our flight. We parked at the ‘Marathon’ gas station as the parking was relatively inexpensive ($6 a day compared to $15 or $20 in the Center of Gatlinburg) and also we planned to go <a href="https://obergatlinburg.com/">Ober Gatlinburg</a> which was just 4 blocks away from the ‘Marathon’ gas station. We highly recommend getting coupons from <a href="https://smokymountaincouponbook.com/">Smoky mountain coupon book</a> which might save you a couple of dollars off of the Aerial tramway tickets amongst other stuff at Ober. Aerial tram is huge and can accommodate around 120 people and transport them to the top of the mountain. You get good views of Gatlinburg as well as the mountains atop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O927o-MNu9HnCTBZy4BlpQ@2x.jpeg" /></figure><p>At the top of the amusement park and ski area that can be accessed by the aerial tram, there are many gift shops, food courts, activities that we can do. I’d recommend trying out few activities while there such as Ice skating, mountain coaster, Alpine slide, wildlife encounter etc. depending on your time and interest. We wanted to see a black bear so bad so we went into the ‘Wildlife encounter’. Each activity has a separate ticket and the price varies depending on the activity. We had our lunch at one of the food courts in the amusement park on top but were not satisfied with the quality, won’t recommend the pizza there. We had seen some cool wild animals such as bears, gray and red fox, turkey vulture, owls etc. in captivity at the ‘Wildlife encounter’ and the official there educated us about the ‘river otters’, their lifestyle, food etc. that were present.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*9xGo7O5aDCj2QYR7YuxGnQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I5QJZmwjCWy4ypat4-kbvw@2x.jpeg" /></figure><p>We descended to the town of Gatlinburg via the aerial tramway and then started our journey back to the Nashville airport resulting in the culmination of a fantastic trip to the Great Smoky Mountain National Park, which will bring a lot of great memories to us for the years to come!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L3ZmAz1m7IZLWG2JYMb_gA@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2875901454c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automation Guild 2021 Online Conference — Review]]></title>
            <link>https://anirudh114-prayaga.medium.com/automation-guild-2021-online-conference-review-b5062a060473?source=rss-b0630a5ff9f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5062a060473</guid>
            <dc:creator><![CDATA[Anirudh Prayaga]]></dc:creator>
            <pubDate>Thu, 18 Feb 2021 16:13:29 GMT</pubDate>
            <atom:updated>2021-02-18T16:13:29.475Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Automation Guild 2021 Online Conference — Review</strong></h3><p>Automation Guild 2021 is a 5 day online conference where test automation experts with diverse backgrounds and expertise share their knowledge and experience across various topics. It is an event conducted annually by Joe Colantonio and this was the 5th and largest event by registrations (~800 people) till date. This year it was held from Feb 8–12 and there were more than 30 speakers from different parts of the world. They had two sections of the conference one for Functional testing (Day 1–3) and the other for Non-Functional testing (Day 4–5). They discussed various topics ranging from API automation testing , test data management, mobile app automation testing, accessibility automated testing, performance testing to name a few.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H_eAd1dTbqu7c-Fz0yIFrg.png" /><figcaption>source : <a href="https://guildconferences.com/wp-content/uploads/2019/08/Round-Guild-Logos-AG-With-text.png">https://guildconferences.com/wp-content/uploads/2019/08/Round-Guild-Logos-AG-With-text.png</a></figcaption></figure><p>I always look forward to this time of the year as it is a great opportunity for me to learn awesome things in the world of automation from the experts and to connect and chat with other test automation pros via the slack channel (https://automationguildconf.slack.com) and stay updated with the latest trends in the test automation space.</p><p>As I was attending this conference during the work week and had meetings and other work related stuff parallely going, obviously I was not able to attend all of the sessions. I was able to summarize the talks that I was able to attend and found interesting below.</p><p><strong>DAY1:</strong></p><p><strong>Test Automation is Not (just) Automating Tests by Rick Martin</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WSqVh-FqBrRCGxP0" /><figcaption>Photo by <a href="https://unsplash.com/@wocintechchat?utm_source=medium&amp;utm_medium=referral">Christina @ wocintechchat.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Rick Martin discusses how test automation is influenced by and influences every aspect of Software Development Life Cycle (SDLC). He discusses an important point to automate the behavior, not the manual test cases directly as manual tests serve just as a guide and not as a precise recipe. Test automation should benefit the whole team and business and shifting left will definitely be of huge help. Shifting left will enable the whole team to understand the requirements in large detail and rope in devs for unit testing, devops engineer for CI and how often to run these tests and what reporting should look like, product owners will benefit from getting important feedback from other team members for use cases and requirements in general.</p><p>Test automation is software development+ and the test code should be written with simplistic beauty and should be understandable, maintainable. One should not automate everything but apply test automation ROI and give more time for exploratory testing. Test automation is not test case automation. These are related but different. Test automation should not be considered for reducing the cost and overhead of testing. By saying so we are ignoring the larger value test automation brings to the table. Using record and playback is test case automation not test automation. Test automation requires you to look at the entire SDLC (waterfall or agile). Look for the biz value to be achieved and how to allocate specific tests to achieve those goals. Test automation is a habit!</p><p>Requirements : Need to be sure that reqs give us appropriate information to do the job. We should be able to verify if they are complete, clear, correct, consistent, testable? Definition of done should include both manual and automated testing.Architecture : During this phase, we need to assess how early we can address non-functional reqs if at all. The factors such as reliability/safety, precision, scalability must be taken into consideration.</p><p>Design : SOLID is a design technique that is robust. Single Responsibility, Open-closed(Open for extension, closed for modification), Liskov Substitution, Interface Segregation (2D, 3D methods should be separated using Interfaces), Dependency Inversion(High level modules should not depend on low level modules) and our test automation framework should comply by these principles. For Implementation these factors should be taken into account: should we be using static analysis or Test Driven Development (TDD), Behavior Driven Development(BDD), Acceptance Test Driven Development(ATDD) and what is the definition of done (DOD) for both manual and automated tests and to test both positive and negative scenarios. Test automation should not be a post release activity.</p><p>During &amp; Post Deployment : We should be testing in the production environment as a part of deployment. Synthetic Transactions(health checks), Monitors and Alarms (to adequately protect the systems), Chaos Engineering (resiliency and recoverability from falls, lack of service from a 3rd party) should be a part of the overall test automation strategy.</p><p><strong>Julia Pottinger : Next Level API Automation: Testing the Boundaries</strong></p><p>In this talk Julia discusses how to efficiently test the API for automation and implementing both the positive and negative test scenarios to thoroughly test the APIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bRM84oUKhv-lddTp" /><figcaption>Photo by <a href="https://unsplash.com/@lazycreekimages?utm_source=medium&amp;utm_medium=referral">Michael Dziedzic</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We normally test positive scenarios for API automated tests but we need to test the negative scenarios as well and ensure the correct error message is shown up and verify that we are not allowed the access if the current token or access code is not provided. We need to also verify the schema for the response that is being returned. Out of lot of different tools, ‘Xhr’ can be used for API testing, ‘frisby’ as well can be used, so are ‘super test’ (http assertions are easy with superagent), ‘chai http’ (integration testing using chai assertions and regular API testing), ‘Cypress’(to make http requests), ‘Chakram’ (Rest/Graph QL APIs), this works along with Mocha (BDD Framework).</p><p>She demonstrated the verification of these three scenarios using ‘chakram’ : 1. Verifying the APIs with schema, 2. verifying errors and 3. verifying workflows in APIs and making sure they are working properly.</p><p>Using jsonschema.net we can generate schemas that can be used to validate the APIs. It ensures the responses are structured correctly and to check the values in the response are of a certain type. She used the ‘chakram’ command to verify the response to have the same schema. Additionally We can also check the status of the response and the header type using ‘chakram’.</p><p>Good advice when we do API automation is always have negative tests (like invalid API key or invalid POST request, input data-type mismatch , sending reqs with invalid names etc. and verifying the status codes/error messages for these such as for 400, 401, 403, 404 etc.). She also demoed how to test the multi step API workflow using chakram(using POST, GET methods). This is similar to using one request’s data in another request for verification. Let’s say we use a POST req to create a record and get the ID of that record and verify the details of that record using a GET request aka Chaining the requests and then updating the record.</p><p><strong>Titus Fortner : Managing Your Data with Abstractions</strong></p><p>In this talk Titus focuses on the usage of test data in the automated test suite and how to effectively manage it without having to deal with maintenance issues. He suggests avoiding data driven testing and any implementation that uses data in a way that does not provide semantically useful information to our tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2yiItYRS7QKFEMge" /><figcaption>Photo by <a href="https://unsplash.com/@swimstaralex?utm_source=medium&amp;utm_medium=referral">Alexander Sinn</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There are 8 major components of a good test automation framework. One of the 8 components that often gets overlooked is managing the test data. Abstracting away implementation details from your tests is just as important for data as it is for the display. He then went over the basics of test data management and demoed an example using java code(reflections) for managing the abstraction strategy effectively.</p><p>8 components of Test Framework are Assertions on Actions, Initialization and cleanup, Configuration data, Data modeling, site modeling abstractions, synchronization strategy, wrappers and helpers, API usage. He focussed on Data Modeling. He suggests writing our tests declaratively(which focuses on ‘what’, ‘biz logic’, ‘big picture’, ‘contextual data’) instead of imperatively(‘How’, ‘Implementation logic’, ‘specific details’, ‘all data’). He then demoed it with an example.</p><p>He discussed the 4 major approaches to Test Data Management.</p><ul><li>Grab and Hope — Use the first available option on the site.</li><li>Static Reference — Traditional QA staging Environment : list correlating existing data to specific tests.</li><li>Dynamic Fixtures : Inject data into the database at the beginning of the test run.</li><li>Just in time : Each test is responsible for all of its own data.</li></ul><p>The underlying idea being — the only way to scale your tests is to run them in parallel and to achieve this the tests should run autonomously. The way to achieve this is the ‘Just In time’ approach. This means every single test is responsible for all of its own data. As he demonstrates this with an example he suggests how awesome ‘Faker’ library is. ‘Faker’ gives us useful semantically relevant methods with a lot of control over exactly what goes where, pretty much anything that can be put in a form can be pulled from a ‘faker’ library.</p><p><strong>DAY2:</strong></p><p><strong>Eran kinsbruner: Key Mobile App Trends &amp; What They Mean for Dev &amp; Testing</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WZ1gq0NsyBM-AHOs" /><figcaption>Photo by <a href="https://unsplash.com/@rmrdnl?utm_source=medium&amp;utm_medium=referral">Daniel Romero</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Eran’s talk mainly focuses on key mobile app trends and what they mean for dev and testing and things to focus on 2021 and beyond regarding the same.</p><p>He talks about ‘Apple appclips’ which are a part of iOS14 : subset of native mobile app (it gives us a sneak peek of the app and as a user we can see the app’s functionality without actually going to the app store and downloading it). ‘Foldables’ : Many big players in the market are currently working on creating these foldable mobile devices. It is a totally different approach and consideration for these phones when compared to the traditional smartphones. He suggests, ‘PWAs’ : Progressive Web Apps will be trending in the mobile space for 2021.</p><p>He discusses ‘Android APKs’ : Zip of smaller android apps which are very unique to a specific set of devices and geography with a dedicated set of functionalities. ‘Big Data and Test Impact Analysis’ will be critical as we move more and more towards continuous testing in the devops phenomena. Mobile test automation frameworks such as ‘Appium’, ‘espresso’, ‘XCUITest’ and ‘Flutter’ are being standardized.</p><p>A tester need to focus on below mentioned Generic Mobile App Testing Considerations for an efficient mobile testing strategy :<strong> ‘</strong>App Functionality’(Biz flows, UI testing, cross platform coverage), ‘real env condition testing’(Network conditions, Interruptions (Calls/Texts/Alerts) Background/Gestures), ‘Non-Functional Testing’(Security/Accessibility/Performance/Availability/API Testing). All these must be shifted left as much as possible and should be integrated in the CI/CD pipeline.</p><p>He then discusses platform specific mobile test automation frameworks for iOS and android (Espresso/XCUITest) and cross platform frameworks for ioS and Android(Appium/Flutter) and how they are implemented.</p><ul><li>Espresso — Java within android studio for android apps</li><li>XCUITest — Objective-C/Swift test creation within Xcode for iOS apps.</li><li>Appium — Webdriver Language bindings</li><li>Flutter — Dart scripting &amp; Appium/Flutter</li></ul><p>Although ‘Appium’ is the leading framework for cross platform mobile automated testing, the best way to test native apps in an efficient way is to use the specific frameworks.</p><p>‘APKs’ are typically the zip files that consist of single APK files, based on rules, specific devices and user requests these files will get installed and enabled on the devices in production. Every app needs to be publishing APKs that are being mandated by Google from the second half of 2021.</p><p>Benefits and deployment options for APKs</p><ul><li>Application binary sizes.</li><li>Overall resource consumption (CPU, battery etc.)</li><li>The ability to gradually expose as well as enable/disable specific modules and features based on customers countries, requirements and other considerations.</li></ul><p>He also mentions important considerations for testing App Clips using various distribution methods such as NFC tags, QR codes, Safari App Banner, Links in messages, Place cards in Maps, Recently used App clips. Also, some of the key areas to test on foldable devices are App continuity/extension, multi window capabilities main and cover displays, making the app sizable, splitview, UI layout, multi OS compatibility, resource consumption, accessibility in foldable devices.</p><p><strong>Lauren Clayberg &amp; Anton Hristov: Testing in Fast-Paced Delivery Organization</strong></p><p>As the title of the talk suggests, the speakers will give us a deeper insight on what entails testing in a fast paced delivery environment and how they utilize ‘mabl’ to achieve this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/1*OW0XC-CqMFhJingCMIJ3nQ.jpeg" /><figcaption>source : <a href="https://s27389.pcdn.co/wp-content/uploads/2020/04/automating-six-cs-devops.jpg">https://s27389.pcdn.co/wp-content/uploads/2020/04/automating-six-cs-devops.jpg</a></figcaption></figure><p>Devops is a fast paced environment and testing is becoming more of a bottleneck with this fast paced environment and testing is becoming more important than ever because of the competitiveness and testing is becoming critical and we should include it earlier in the devops pipeline. Testing in DevOps : Consists of testing in ‘code’ , ‘pull request’, ‘deploy’, ‘run’ phases. Unit tests are great and integration testing is different pieces of code working together, E2E tests are essential and considered best practices for User Experiences. Exploratory testing is very critical as it can find the defects which automated testing cannot.</p><p>Speakers then discussed the testing strategies at ‘Mabl’. ‘Mabl’ has a chrome extension and a CLI tool and desktop app that we can make use of. Team also uses ‘Mabl’ to test any web app. They use mabl for Unit, integration, E2E testing and they do a team based Exploratory where they get together and sit in a room and test the application to find any uncaught bugs. Speakers Demoed ‘mabl’ on ‘mabl’ workspace setup for testing including mabl DevTestOps pipeline , monitoring their production app and using insights to understand product quality</p><p>KeyTakeaways for any team would be to test at every step(code, build, deploy, run) of your deployment process to catch issues early. Looking for ways to integrate your testing tools with your Workflow and analytics tools so that everyone is more informed and productive. Determining wastes and coverage gaps in the E2E tests and measures to rectify them. Testing in production environments to proactively monitor for regressions, especially in 3rd party services.</p><p><strong>DAY3:</strong></p><p><strong>Shriram Krishnan &amp; Guljeet Nagpaul: Full Stack Automation -How to get it right!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPBWUJm_ntl1SC4uJNTy0w.jpeg" /><figcaption>source : <a href="https://cdn.helpsystems.com/styles/crop_general/storage-api-public/am-bpa-tools-1200x628_0_0.jpg?itok=cuHqDxXz">https://cdn.helpsystems.com/styles/crop_general/storage-api-public/am-bpa-tools-1200x628_0_0.jpg?itok=cuHqDxXz</a></figcaption></figure><p>The speakers kicked off the session by giving a brief history of test automation. They emphasized on how the prominence of web automation has risen in the early part of last decade and how the importance unit and API automation has been increasing in the latter part of the decade and the steep rise of ‘Mobile and continuous’ testing from 2018.</p><p>Now is the time ‘Full stack automation’ has almost become a need. Main reason being increasing focus on customer experience. Also, app architecture is more componentized and integrated. CI/CD and agile development is bringing in faster rate of change and we need ‘Full stack automation’ to have confidence in our system that our app’s customer experience is top notch.</p><p>As the different types of automated tests that have evolved, the validations for API, UI, Backend are all done independently and that is a challenge in the fullstack automation. Due to which there are some dis-integrated frameworks being developed and it is a challenge.</p><p>The speakers then discuss the key considerations for success. Integrated frameworks are the first thing that we can take advantage of as they are cross invocable, pluggable anywhere in the E2E chain. The framework has to be adaptable and extendible. Being able to share the data across tech stacks is a key component. The framework needs to be manageable and traceable — Life Cycle is linked together. Speakers then demoed a scenario where the full stack automation can be done right using ‘AccelQ’.</p><p><strong>DAY4:</strong></p><p><strong>Pragati Sharma : Accessibility Automation Testing</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*_ofqz4bq5R_oAW7SjFyvPA.jpeg" /><figcaption>source : <a href="https://cdn3.vectorstock.com/i/1000x1000/53/22/accessibility-icon-vector-25025322.jpg">https://cdn3.vectorstock.com/i/1000x1000/53/22/accessibility-icon-vector-25025322.jpg</a></figcaption></figure><p>Speaker starts the session off by introducing us to what accessibility testing is all about and why we need it. She brings a good point regarding the potential of accessibility testing as around 20% of the world’s population is disabled and how the apps we develop need to cater their needs as well. She gives an example of subway stairs vs ramps in stressing the importance of accessibility is not only targeted to a specific group but on a holistic basis it enhances the user experience.</p><p>She focuses on the financial aspect of accessibility testing by giving an example of a scenario where an online content streaming company $750,000 when a lawsuit was filed as they did not have closed captions (CC) enabled.</p><p>She demonstrated an example of automated accessibility tests using ‘Cypress’ and ‘AXE’. ‘AXE’ can be used with various languages and there is a chrome plugin for ‘AXE’ which a user can make use of to detect accessibility violations in a manual fashion. She then explained the ‘Cypress project structure’ that she used for the accessibility automation. Following that she explained how we can run accessibility tests against a specific standard such as ‘wcag2a’, ‘wcag2aa’ etc.</p><p>Before we address the accessibility needs, we need to analyse what kind of application is ours and how our users are using our app and a survey of what kind of specific accessibility needs(eg: vision vs audio) we need to address so that our user’s experience is enhanced.</p><p><strong>DAY5:</strong></p><p><strong>Mohamed Labouardy : Pipeline as Code</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9mbLnEzhr7xvBQwQJDX5g.jpeg" /><figcaption>source : <a href="https://images.techhive.com/images/article/2017/02/pressure-water-line-100707995-large.jpg">https://images.techhive.com/images/article/2017/02/pressure-water-line-100707995-large.jpg</a></figcaption></figure><p>In this session, the speaker shows how we can run automated tests using the ‘pipeline as code’ approach with an example.</p><p>In this example, he uses Jenkins in a distributed mode. We have Jenkins master and jenkins workers. Jenkins master schedules jobs on available jenkins workers. The workers running inside the CI/CD pipeline based on the stages defined in the jenkins file. Here he uses the ‘SonarQube’ tool to continuously inspect the quality of source code. He also uses ‘anchore’ which is used to run security tests on ‘docker’ images before he pushes the code to prod servers and at the end he will be deploying AWS servers.</p><p>He uses ‘terraform’ to configure the jenkins ‘masters’ and ‘workers’ and when an additional worker should be scaled. He has a jenkins file which has multiple stages the first one being the checkout stage, this fetches all the changes from the github repo and then builds the docker image based on dockerfile.test in his project. In his docker image, he installs the native dependencies and copies the source code to that docker container and installs chromium to run tests in a headless fashion. He then runs the ‘lint’ which checks the source code for programmatic, syntactic errors. It makes the app in a uniform format.</p><p>The next stage is running the unit tests, here unit tests are run using headless chromium, this inturn generates a coverage report. The next stage is running ‘sonarqube’ for static code analysis which he pre-defines in the sonar.project properties as to what folders in the source code it needs to analyse. If there are no issues, we move to the ‘build’ stage where docker image is triggered which builds the application. We then push it to the docker registry. The next stage is to analyze any security vulnerabilities of the docker image. If all these stages are successful we will deploy. Then the speaker showed how it all works using a real time example and the stages and results of each stage in jenkins.</p><p><strong>EPILOG</strong></p><p>This was one of the best conferences I’ve attended with a lot of new learnings from the speakers and the slack community. Thanks to Cory Schmidt, for encouraging me to attend these sessions and kudos to Joe &amp; team for making this happen and taking this to another level. It is just intriguing to know how things are changing in the test automation space rapidly year by year especially with AI getting into the picture. As always, I’m excited for the next year’s event and look forward to it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5062a060473" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>