<?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 Rino Abraham on Medium]]></title>
        <description><![CDATA[Stories by Rino Abraham on Medium]]></description>
        <link>https://medium.com/@rinoabm?source=rss-3ce6f0a49d65------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3ANix8ipg6jIUiPu_wJK7Q.jpeg</url>
            <title>Stories by Rino Abraham on Medium</title>
            <link>https://medium.com/@rinoabm?source=rss-3ce6f0a49d65------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:31:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rinoabm/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[Automating Azure Test Plan with powershell scripting]]></title>
            <link>https://medium.com/@rinoabm/automating-azure-test-plan-with-powershell-scripting-122e37004c89?source=rss-3ce6f0a49d65------2</link>
            <guid isPermaLink="false">https://medium.com/p/122e37004c89</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-test-plans]]></category>
            <dc:creator><![CDATA[Rino Abraham]]></dc:creator>
            <pubDate>Sun, 03 Apr 2022 02:14:12 GMT</pubDate>
            <atom:updated>2022-04-03T02:14:12.871Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*e-PUzANA8m7dC490" /></figure><p>Ever wondered how to automate the test-results into Azure Test Plan via external scripts this article will help in achieving the same. Azure does not provide the capability of running Azure test plan directly out of the box for test frameworks like Jnuit, TestNg which is used in most of java based projects. At present this capability Azure has leveraged mainly with .Net core framework projects and some others.</p><p><a href="https://docs.microsoft.com/en-us/azure/devops/test/associate-automated-test-with-test-case?view=azure-devops">Associate automated tests with test cases - Azure Test Plans</a></p><p>Refer above article from Microsoft to find out more. However using Azure Test Plan APIs you can still achieve this feat using external scripts and for this article we will be learning the same using powershell, test framework used here is Cucumber with Junit</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*zeg_PddIrKLfLU52y_9QjQ.png" /><figcaption>technologies involved</figcaption></figure><p><strong>First prerequisite of making use of Azure APIs is to have a PAT(Personal Access Token).</strong> This can be created in Azure portal user settings sections https://dev.azure.com/{organization_url}/_usersSettings/tokens, this token is required for establishing the communication channel.</p><p>To test out if the communication channel is established you can make use of this PAT token and check if you are able to retrieve all the test plans &amp; test suites with powershell. <em>Please note orgUrl, projUrl, pat has to be defined by you.</em></p><pre>#<strong> Define organization base url, PAT and API version variables</strong> <br>$orgUrl = &quot;https://dev.azure.com/{orgUrl}&quot;<br>$projUrl = &quot;{projUrl}&quot;<br>$apiVersion = &quot;api-version=5.0&quot;<br>$pat = &quot;YourPersonalAccessTokenNeedstoBePlacedHere&quot;<br><br><br># <strong>Create header with PAT</strong><br>$token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(&quot;:$($pat)&quot;))<br>$header = @{authorization = &quot;Basic $token&quot;}<br><br># <strong>Get all the test plans for the project</strong><br>$getAllTestPlans = &quot;$orgUrl/$projUrl/_apis/test/plans?$apiVersion&quot;<br>$testPlans = Invoke-RestMethod  -Uri $getAllTestPlans -Method Get -ContentType &quot;application/json&quot; -Headers $header<br>echo $testPlans.value<br><br># <strong>Get all test suites for a test plan</strong><br>$getAllTestSuites = &quot;$orgUrl/$projUrl/_apis/test/plans/$projectTestPlanID/suites?$apiVersion&quot;<br>$testSuites = Invoke-RestMethod  -Uri $getAllTestSuites -Method Get -ContentType &quot;application/json&quot; -Headers $header<br>echo $testSuites.value</pre><p>If the response to above scripts is a valid 200 response and you could see the Test Plans defined in your Azure portal and its suite information then you are on track. Now let’s assume you have a build run and for cucumber tests you have a report generated and you need to update this test results into Azure test plan same can be achieved with below script</p><p><strong>Step1 : Get all test points for a test suite</strong></p><pre># <strong>Get all test points for a test suite</strong><br>$getAllTestPoints = &quot;$orgUrl/$projUrl/_apis/test/plans/$projectTestPlanID/suites/$projectTestSuiteID/points?$apiVersion&quot;<br>$testPoints= Invoke-RestMethod  -Uri $getAllTestPoints -Method Get -ContentType &quot;application/json&quot; -Headers $header<br>$getTestPointsId = $testPoints.value.id -join &#39;,&#39;  <br><br>$test = &quot;[$getTestPointsId]&quot; <br>echo $test</pre><p><em>$projectTestPlanID &amp; $projectTestSuiteID needs to be decided by you.</em></p><p><strong>Step2 : Create a test run</strong></p><pre>#<strong>create test run</strong><br>$createTestRun = &quot;$orgUrl/$projUrl/_apis/test/runs?$apiVersion&quot;<br>$testRunData = @&quot;<br>    {<br>        &quot;name&quot;:&quot;DemoRunTest&quot;,<br>        &quot;plan&quot;:{&quot;id&quot;:{TestPlanID}},<br>        &quot;pointIds&quot;:[$getTestPointsId]<br>    }<br>&quot;@<br><br><br>$testRunInformation = Invoke-RestMethod -Method &#39;Post&#39; -Uri $createTestRun -Body $testRunData -Headers $header -ContentType &quot;application/json&quot;<br><br>$testRunId = $testRunInformation.id</pre><p><em>Again {TestPlanId} needs to be your test plan id.</em></p><p><strong>Step3 : Get test result ID</strong></p><pre><strong>#get test result ID </strong></pre><pre>$getTestResultInformation = &quot;$orgUrl/$projUrl/_apis/test/runs/$testRunId/results?api-version=6.0-preview.6&quot;<br>$testResultID = Invoke-RestMethod  -Uri $getTestResultInformation  -Method Get -ContentType &quot;application/json&quot; -Headers $header<br>echo $testResultID</pre><p><strong>Step4 : Function to read results from cucumber.json</strong></p><pre>#<strong>function to read from cucumber.json</strong></pre><pre>[string]$updateTestResultBody = @()<br>$cucumberJsonObj =Get-Content &#39;C:\Folder\cucumber.json&#39; | Out-String | ConvertFrom-Json<br>$filterCucumberObj= $cucumberJsonObj.elements | Where-Object -Property name | Select-Object -Property name,after<br>echo $filterCucumberObj<br>                $j=100000<br>Foreach ($i in $filterCucumberObj){<br><br>    If ($i.name -match &#39;^\D*(\d{6}).*$&#39;) {<br>        $testCaseID = $Matches[1]<br>        echo $tesCaseID<br>    } else {<br>        $testCaseID = &quot;No Match for TestCaseID&quot;<br>    }<br>    $testCaseID<br>    $outcome = $i.after[0].result.status.ToUpper()<br><br>    echo $outome<br><br>    $result +=  @&quot;<br>{<br>    &quot;id&quot;:$j,&quot;outcome&quot;:&quot;$outcome&quot;,&quot;state&quot;:&quot;Completed&quot;,&quot;comment&quot;:&quot;Execution Successful&quot;<br>},<br>&quot;@<br>     $j += 1<br><br><br>}<br><br> $updateTestResultBody =$result.TrimEnd(&quot;,&quot;)<br> $result = @()<br><br> $test= &quot;[$updateTestResultBody]&quot;</pre><p><strong>Step5 : Update results in test run</strong></p><pre>#<strong>Update Results in Test Run</strong><br><br>$updateResultInTestRun = &quot;$orgUrl/$projUrl/_apis/test/runs/$testRunId/results?api-version=6.0-preview.6&quot;<br><br><br><br>$testRunId = Invoke-RestMethod -Method &#39;Patch&#39; -Uri $updateResultInTestRun -Body  $test  -Headers $header -ContentType &quot;application/json&quot;</pre><p>Eventually if all your requests are completed without any error you could see your test run results in Azure portal.</p><p>Hope this information helps you in your work, for more collaboration connect with me on linkedin</p><p><a href="https://www.linkedin.com/in/rino-abraham-a926147a/">Rino Abraham - Engineer - Siemens Technology India | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=122e37004c89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to improve “Bug” workflow in agile world]]></title>
            <link>https://medium.com/@rinoabm/bug-workflow-in-agile-world-7b9c5a203569?source=rss-3ce6f0a49d65------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b9c5a203569</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[bug-tracking]]></category>
            <category><![CDATA[bug-fixes]]></category>
            <dc:creator><![CDATA[Rino Abraham]]></dc:creator>
            <pubDate>Thu, 03 Mar 2022 14:03:57 GMT</pubDate>
            <atom:updated>2022-03-03T14:15:23.125Z</atom:updated>
            <content:encoded><![CDATA[<p>In Agile world where in sprint on sprint we target to release new version of product, it is very important to capture bugs at early stage and it is even more important on how we treat these bugs when we find out one, as bug is an “Uncertain” event which no one expects. In this article I will illustrate an example of how to ensure smooth workflow of a bug from the event of it being found till how we should ensure closure of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*InLm37CLu4t8A5Jh" /><figcaption>~ if it can fly it should die ~</figcaption></figure><blockquote><em>Well a bug in a product is an adversity for all the stakeholders which when found creates a panic especially if its found by an end user in production environment. And in most of the cases it happens that this bug was fixed in previous environment however still gets migrated into production, on asked to a QA(quality assurance) team member by Product Owner for an explanation of the same there is hardly anything left to be told, but a good product owner during this phase should be asking </em>“how we can stop this from happening again” ? <em>which is a rare sight to see.</em></blockquote><p>It was seen in one of the project where in the release was happening at a higher rate and almost all the stories planned were getting closed that even the bugs get closed in same sprint, which raised a curiosity in my mind on how good the relation should be in such a team between a developer and tester that they could fix a bug, tester could validate the bug and move to higher environments within a 2 week sprint. On further investigation I found that the “Originator”(tester who raised the bug) was never given the bug again back for verification and only during sprint demo that the developer would show in quick glance the fix being worked and the bug was getting closed. Which did explain the fast delivery, however it was difficult to explain the team on important thing that the bug is not really dead, it’s still flying around the environments.</p><p>Below diagram was then illustrated to the team on how we could improve the situation and I hope it helps your team where the situation is same</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*288cgB5NUZdLK81KCMBHEg.png" /><figcaption>(illustration of bug workflow that can be easily adapted in agile projects)</figcaption></figure><p>Some key points to keep things very simple</p><ol><li>As a <strong>product owne</strong>r you should never pressurize the team to gets bugs fixed in one sprint, allow them to have a proper root cause inspection</li><li>As a <strong>developer </strong>ensure that with the fix your unit test case is also adapted. As unit test cases is the bottom layer of test automation which should be well maintained</li><li>As a <strong>tester </strong>you should never test the bug in the same environment where the bug was fixed, probably do in your own test environment. Also before the bug closure it is very important that the corresponding test cases automated are also adapted.</li></ol><p>Above 3 rules if followed will help in your agile projects to steer a much healthy release of your product to the market. Hope the above article helps you in your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*4QeEXG4ZPdST7eKqNCwU6g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b9c5a203569" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>