<?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 Muntasir Abdullah Mizan on Medium]]></title>
        <description><![CDATA[Stories by Muntasir Abdullah Mizan on Medium]]></description>
        <link>https://medium.com/@muntasir.?source=rss-8747f953f5d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*slrW_YVpEyGVQeXI3H6KFA.jpeg</url>
            <title>Stories by Muntasir Abdullah Mizan on Medium</title>
            <link>https://medium.com/@muntasir.?source=rss-8747f953f5d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:55:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@muntasir./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[Encrypted Login Automation using Selenium]]></title>
            <link>https://medium.com/@muntasir./encrypted-login-automation-using-selenium-36c9e3206fbc?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/36c9e3206fbc</guid>
            <category><![CDATA[selenium-test-automation]]></category>
            <category><![CDATA[encryption]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Mon, 31 Aug 2020 05:23:01 GMT</pubDate>
            <atom:updated>2020-08-31T05:46:05.195Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*Q_hmPOH4qw7X96KlP62bhA.jpeg" /><figcaption>Encryption</figcaption></figure><p>Sometimes we don’t want to expose our real test data to public. Suppose we want to automate login test case by our real Email and Password. When we share common test case but want to use our own data. In automation project we use Login Test class but use use our own data that we don’t want to expose.</p><p>Today i am gonna share with you how can we hide our credentials when testing.</p><p>First we have to store our Password in notepad file.</p><p>For read this password I have to create a method and named it getEncodePassword() in this method I read notepad data and Encode it.I encode as a byte[]. This data we use for login. But we know that in Selenium sendKeys() methods only accept String value. So that we need to convert this as String. But problem in we cant pass Encode value in sendKeys() because it is not real password and login failed obviously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K59XOHSfkWNSdBjB1xxXZg.png" /><figcaption>Encode Password</figcaption></figure><p>Now I need to Decode this. I create another method named getDecodepassword()</p><p>I need to decode this value for use this for Login. So that i pass this value in sendKeys()</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*l0CalauairlMZZIwPo71cw.png" /><figcaption>Decode</figcaption></figure><p>Now I implement this Decode password in login Test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/1*nZG9IamMdzSyuwzeHbErMQ.png" /><figcaption>Use decode password in Login</figcaption></figure><p>when I run this test case, Firefox browser launch, Test URL open, input email that provide directly in this test case, input password that we read from notepad. Finally it login when i use real email and password.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36c9e3206fbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rest Assured GettingStarted]]></title>
            <link>https://medium.com/oceanize-geeks/rest-assured-gettingstarted-7beff2bc6305?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7beff2bc6305</guid>
            <category><![CDATA[api-testing]]></category>
            <category><![CDATA[restassured]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Fri, 24 Jul 2020 10:03:59 GMT</pubDate>
            <atom:updated>2020-07-24T10:21:49.913Z</atom:updated>
            <content:encoded><![CDATA[<h3>Rest Assured Getting Started</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*9p86tphgBGlkJRaX3koyuQ.jpeg" /><figcaption>Rest Assured</figcaption></figure><h3>REST Assured for Maven users</h3><p>Maven:</p><pre>&lt;dependency&gt;<br>      &lt;groupId&gt;io.rest-assured&lt;/groupId&gt;<br>      &lt;artifactId&gt;rest-assured&lt;/artifactId&gt;<br>      &lt;version&gt;4.3.1&lt;/version&gt;<br>      &lt;scope&gt;test&lt;/scope&gt;<br>&lt;/dependency&gt;</pre><p>Notes</p><ol><li>You should place rest-assured before the JUnit dependency declaration in your pom.xml / build.gradle in order to make sure that the correct version of Hamcrest is used.</li><li>REST Assured includes JsonPath and XmlPath as transitive dependencies.</li></ol><h3>TestNG</h3><p>Maven:</p><pre>&lt;dependency&gt;<br>      &lt;groupId&gt;org.testng&lt;/groupId&gt;<br>      &lt;artifactId&gt;testng&lt;/artifactId&gt;<br>      &lt;version&gt;7.1.0&lt;/version&gt;<br>      &lt;scope&gt;test&lt;/scope&gt;<br>&lt;/dependency&gt;</pre><h3>JsonPath</h3><p>Standalone JsonPath (included if you depend on the rest-assured artifact). Makes it easy to parse JSON documents. Note that this JsonPath implementation uses <a href="http://groovy-lang.org/processing-xml.html#_gpath">Groovy&#39;s GPath</a> syntax and is not to be confused with Kalle Stenflo&#39;s <a href="https://github.com/json-path/JsonPath">JsonPath</a> implementation.</p><p>Maven:</p><pre>&lt;dependency&gt;<br>      &lt;groupId&gt;io.rest-assured&lt;/groupId&gt;<br>      &lt;artifactId&gt;json-path&lt;/artifactId&gt;<br>      &lt;version&gt;4.3.1&lt;/version&gt;<br>      &lt;scope&gt;test&lt;/scope&gt;<br>&lt;/dependency&gt;</pre><h3>XmlPath</h3><p>Stand-alone XmlPath (included if you depend on the rest-assured artifact). Makes it easy to parse XML documents.</p><p>Maven:</p><pre>&lt;dependency&gt;<br>      &lt;groupId&gt;io.rest-assured&lt;/groupId&gt;<br>      &lt;artifactId&gt;xml-path&lt;/artifactId&gt;<br>      &lt;version&gt;4.3.1&lt;/version&gt;<br>      &lt;scope&gt;test&lt;/scope&gt;<br>&lt;/dependency&gt;</pre><h3>JSON Schema Validation</h3><p>If you want to validate that a JSON response conforms to a <a href="http://json-schema.org/">Json Schema</a> you can use the json-schema-validator module:</p><p>Maven:</p><pre>&lt;dependency&gt;<br>      &lt;groupId&gt;io.rest-assured&lt;/groupId&gt;<br>      &lt;artifactId&gt;json-schema-validator&lt;/artifactId&gt;<br>      &lt;version&gt;4.3.1&lt;/version&gt;<br>      &lt;scope&gt;test&lt;/scope&gt;<br>&lt;/dependency&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPFEzRXcQCW9KQsHv2VSJw.png" /><figcaption>All Dependencies</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aisa2H9dKMD2wVDVpXgn-Q.png" /><figcaption>GET Request</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7beff2bc6305" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/rest-assured-gettingstarted-7beff2bc6305">Rest Assured GettingStarted</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Role of Testers in DevOps]]></title>
            <link>https://medium.com/oceanize-geeks/role-of-testers-in-devops-56e790792cd7?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/56e790792cd7</guid>
            <category><![CDATA[software-qa]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Thu, 05 Sep 2019 08:34:52 GMT</pubDate>
            <atom:updated>2019-09-05T10:10:12.829Z</atom:updated>
            <content:encoded><![CDATA[<p>In order to build, test, and release software faster and more reliably. DevOps introduce some set of practice that automates the processes between software development and IT teams.</p><p>DevOps aimed not only to improve the process of feature releases but also to reduce defects, so that products can gain high level of quality. DevOps reduce the process cost related with delivering working product in incremental approach. DevOps dealing with small, rapid, iterative development.</p><p>The changes that each release having clarity, consistency and collaboration to understand each other. Changes also been affected in production environment and customer environment. QA team design details test plan based on those changes. Operation and development team need to come on same umbrella. This time specified methodology and tools play a vital role. Each team following their own designed methodology that best suit with their skill and process. But goals are common. That is quality products in a very short time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZUIwLExSu3slCz5mu_ETw.png" /></figure><p>Testers and developers both play important roles in DevOps.</p><p>Normally test Process are based on some steps that following all test levels until product ready for final deployment. Consider those activities that describe below.</p><p>a. QA team gets build after it successfully deployed. Here planed test environment is the key factor that influence test.</p><p>b. Then QA team perform test execution based on pre planed test case or without defined test cases.</p><p>c. Test execution may be Manual or Automated.</p><p>d. Functional and Regression testing are main concern.</p><p>After QA team meets exit criteria then they stopped testing. Then this build finally goes into the production server.</p><p>Now think about <strong>DevOps</strong>. In DevOps, test scenario is different from traditional test process. As quickly as possible QA transfer fresh development code into the production environment with the collaboration of the DevOps teams. DevOps engineer then provide the necessary support on tools and infrastructure to make it a process that works perfectly, making sure all changes function behaved as expected.</p><p>QA team should be focused about quality in software development life-cycle. Testers be part of technical teams. Testers have to consider manual functional and non-functional testing, and should focus on their skills and experiences for apply test automation, and define test strategies.</p><p>Testers always think about requirements that must be meet. Testers be focused on every change and their effect on developing products. In order to do this, requirements analysis done by testers. Testers find out test scope. After successfully analysis, quality attributes be well-introduce. Some quality characteristic be pre-defined by organizations or by customers. Requirements need to be specific. QA teams should involve in the requirements process to help and guide development teams. QA teams need to start thinking about how they can utilize their skills to add value as more of their day-to-day work is automated.</p><p>Risk based testing also have large benefits. Testers have to do regression testing when major changes that may affect other functions as well. In this scenario automate regression test play very important role by maximum test coverage.</p><p>QA teams should play positive attitude and try most effective communication way with teams so their technique can add the value by all possible way in the software development life cycle.</p><p>As a tester, the following core tasks need to be maintained through the life cycle.</p><p>a. Engineers and QA activities should be one lined based on standard that expected.</p><p>b. Try to automate test cases.</p><p>c. All deployment must be automated.</p><p>d. Test cases that are automated should be perfectly aligned with the Continuous Integration cycle.</p><p>e. Proper utilization of test automation tools and Continuous Integration tools.</p><p>From a logistical perspective, Ernest Mueller, lean systems manager for AlienVault and organizer of DevOps Days Austin says, there are three likely ways to see QA roles reassigned to better fit DevOps organizations.</p><p>First, there’s the opportunity to embed QA expertise directly within product teams to directly support them. This is an area that has been most effective in dealing with QA transition so far, says Steve Anderson, CEO of the DevOps and agile consultancy Clutch. “The most successful ways I’ve seen where you still get a hybrid going on is where a QA is directly embedded into the sprint team or the scrum team, where they’re involved from the get-go,” he says. “They get the user’s story. They’re writing test cases.”</p><p>Second, Mueller says, there’s also the potential for diverting QA pros into tooling groups responsible for writing the test harness or providing tooling across the organization.</p><p>And third, there’s the opportunity for creating a center of excellence or consulting group meant to advise specific work groups on strategic issues of quality. “That can be tricky, because having the separate consulting group can easily turn into doing it the way you used to work,” he explains. “It’s a very subtle approach change that you have to make. It’s not like they’re not doing work for you. They’re providing expert consulting so you can do the work better.”</p><p>The speed of automation should have QA working within a totally different paradigm, says Wayne Ariola, chief strategy officer for Parasoft, a testing and service virtualization firm. “Today we’re mostly in causal observation mode: Build the test, experience the defect, collect the defect — it’s causal. Something happened, we collected it,” he says. “We need to move to a more probabilistic mode.</p><p>“This means getting to know the internal application much more as testers than we do today,” he says. “This also means we have to understand the dependencies associated with the operational testing.”</p><p>The truth is that there is still plenty of room for testing professionals in the era of DevOps. They just need to adapt to a rewritten organizational hierarchy — and a completely different mindset about testing objectives.</p><p>For maintain higher accuracy on quality, it is necessary to automate all testing processes by accurately configuring for auto deployment. QA team should Keep in their mind that all process should be done without any failure.</p><p>Concentrating on the customer needs, tester give focus on validating product in short time and gaining high level of quality. A good tester should not mess with time and quality when more builds are on pipeline.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56e790792cd7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/role-of-testers-in-devops-56e790792cd7">Role of Testers in DevOps</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Selenium 4 is releasing soon: What every QA must know?]]></title>
            <link>https://medium.com/oceanize-geeks/selenium-4-is-releasing-soon-what-every-qa-must-know-c82d4914be0a?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c82d4914be0a</guid>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[selenium-webdriver]]></category>
            <category><![CDATA[selenium-testing]]></category>
            <category><![CDATA[selenium-test-automation]]></category>
            <category><![CDATA[selenium-software-testing]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Tue, 04 Dec 2018 02:12:00 GMT</pubDate>
            <atom:updated>2018-12-04T02:12:00.747Z</atom:updated>
            <content:encoded><![CDATA[<p>Selenium 4 version is all set to release this Christmas. Simon Stewart (founding member of Selenium) has officially announced at the recently held selenium conference at Bangalore. Some major changes in the upcoming Selenium 4 have been revealed. So, it’s time to get ahead of the curve and figure out what is going to be changed, added and deprecated. In this article, we will take a look a few important features and give an insight on updates you can expect for your automation framework.</p><h3>W3C WebDriver Standardization</h3><p>The Selenium 4 WebDriver will be completely W3C Standardized. The WebDriver API has grown to be relevant outside of Selenium. It is used in multiple tools for automation. For example, it’s used heavily in mobile testing through tools such as Appium and iOS Driver. The W3C standard will encourage compatibility across different software implementations of the WebDriver API.</p><p>Let’s take an example of how Selenium Grid communicates with Driver executables as of now –</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*2CqfdRhjGWqa-mi4tVot8g.png" /></figure><p>A test in Selenium 3.x, at local end (through JSON wire protocol), communicates with the browser at End node. This requires encoding and decoding of API. In Selenium 4, the test will directly communicate without any encoding and decoding of API requests (through W3C Protocol) through java bindings will be backward compatible but focusing more on W3C Protocol.</p><p>The JSON wire protocol will no longer be used.</p><p>There are multiple contributors to WebDriver W3C specs. All of the work done is on GitHub which can be found on- <a href="https://github.com/w3c/webdriver">https://github.com/w3c/webdriver</a></p><h3>Selenium 4 IDE</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*mbLsoaqTIraTnENGeXNfyg.png" /></figure><p>The Selenium IDE support for Chrome is in a bucket. As we all know that Selenium IDE is a record and playback tool. It will now be available with much more rich and advanced features such as:</p><ul><li><strong>New plugin system</strong>– Any browser vendor will now be able to easily plug-in to the new selenium IDE. You can have your own locator strategy and can plug in selenium IDE.</li><li><strong>New CLI runner</strong> — It will be completely based on nodeNodejs and not old HTML based runner. It will have following capabilities-</li><li><strong>WebDriver Playback</strong> — The new Selenium IDE runner will be completely based on WebDriver.</li><li><strong>Parallel execution</strong>- The new CLI runner will also support parallel test case execution and will provide useful information like time taken, the number of test cases passed and failed.</li></ul><h3>Improved Selenium Grid</h3><p>The one who has worked on Selenium Grid must know how difficult it is to set up and configure. Selenium Grid supports test case execution on different browsers, operating systems, and machines. Thus it provides parallel execution capability.</p><p>There are two main elements in Selenium Grid- <strong>Hub </strong>and <strong>Node</strong>.</p><p><strong>Hub- </strong>Acts as a server, a central point to control all the test machines in a network. In selenium grid, there is only one hub which allocates the test execution to a particular node based on capability matches.</p><p><strong>Node- </strong>In simple words node is a test machine where test cases actually run<strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*CW4NTlAFXUtIi3m3ewbieQ.png" /></figure><p>For more details on selenium grid, follow the tutorial here- <a href="https://www.seleniumhq.org/docs/07_selenium_grid.jsp">https://www.seleniumhq.org/docs/07_selenium_grid.jsp</a></p><p>The typical process to setup selenium grid till now caused testers sometimes to face difficulty in connecting node to the hub.</p><p>In Selenium 4 the grid experience is going to be easy and smooth. As there will not be any need to set up and start hub and node separately. Once we start selenium server, the grid will act as both hub and node.</p><p>Selenium 4 will come up with a more stable selenium grid in terms of removing all thread-safety bugs, and a better support for Docker.</p><h3>Better Selenium Grid UI</h3><p>The Selenium 4 would come up with more user-friendly UI of a grid having relevant pieces of information about sessions running, capacity etc.</p><h3>Better Observability</h3><p><em>“Passive observability is the ability to do descriptive tracing.”</em> <br>– Simon Stewart</p><p>Observability, logging and debugging is no more confined to DevOps in recent times. As part of this release request tracing and logging with hooks will be improved so as to provide automation engineers a hold on debugging.</p><h3>Refreshed Documentation</h3><p>Documentation plays a key role in any project’s success. Selenium docs were not updated since selenium 2.0 release. In the latest upgrade selenium documentation is also going to be refreshed and detailed [WIP]. You can access it on — <a href="https://seleniumhq.github.io/docs/">https://seleniumhq.github.io/docs/</a></p><h3>Selenium 4 In a nutshell</h3><p>Upgrading to the latest version of selenium should not require any code changes. Setting up node and hub will become smooth and the entire grid experience is going to be streamlined. For automation engineers, the latest version should not be challenging and existing automation framework should work with minimal changes.</p><h3>More to come</h3><p>These are a few important changes. Stay tuned as there is plenty more to come.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c82d4914be0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/selenium-4-is-releasing-soon-what-every-qa-must-know-c82d4914be0a">Selenium 4 is releasing soon: What every QA must know?</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Testing Hot Cakes for 2018]]></title>
            <link>https://medium.com/oceanize-geeks/software-testing-hot-cakes-for-2018-94d2514e1ab0?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/94d2514e1ab0</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Thu, 03 May 2018 09:08:36 GMT</pubDate>
            <atom:updated>2018-05-03T09:27:16.164Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The</strong> software testing community has experienced the exciting year of 2017 with many trends taking shape. Amid both hypes and actual applications of artificial intelligence (AI) and automation, many developments and challenges in software testing through the year deserve our attention. They include a continuing trend in adoption of DevOps and test automation practices and tools, increasing test automation for web applications along with new and more powerful test automation tools introduced to the market, remaining difficulties in managing test data and environments, shortening release schedules, and the lack of time for testing.</p><p>In reference to the state of software testing in 2017, we here make bold predictions of trends of software testing for 2018 and beyond.</p><h3>1. Increasing Adoption of DevOps</h3><p>DevOps is a set of practices that aim to reduce the time from development (Dev) to operation (Ops) while ensuring the quality of software. According to Google Trends, as shown in the figure below, DevOps has gained an overwhelming interest over the past five years. This trend likely continues in the next few years. We will see more organizations employing DevOps practices more fully. As DevOps practices emphasize on automation and integration, more practices and tools are introduced to support automated testing and continuous integrations.</p><h3>2. More Utilization of Test Automation</h3><p>Although test automation is an essential part of DevOps, it currently only accounts for less than 20% of software testing activities according to <a href="https://www.sogeti.com/explore/reports/world-quality-report-2017-2018/">World Quality Report 2017–2018</a>. Organizations mainly focus on functional UI and regression testing.</p><p>Test automation is seen as the main approach to shortening the testing and delivery time. The capability to integrate with DevOps toolchains becomes a must-have feature of test automation tools. Most major open-source and free tools such as <a href="http://seleniumhq.org/">Selenium</a> and <a href="https://www.katalon.com/">Katalon</a> and commercial tools as <a href="https://www.ranorex.com/">Ranorex</a> and <a href="https://smartbear.com/product/testcomplete/overview/">TestComplete</a> now support integration with many DevOps toolchains like Jenkins, GIT, and JIRA.</p><h3>3. Combining Manual and Automated Testing</h3><p>Although test automation is a hot keyword today, manual testing is still dominating in the QA and testing industry. This state of software testing makes it hard to address challenges in ever shortening delivery cycles and complex test environments and data. Combining manual and automated testing practices and tools is likely a continuing trend in the next few years. Right testing strategies are those that take advantages of both manual and automated approaches.</p><h3>4. Intelligent Test Automation and Analytics</h3><p>AI and machine learning techniques have been applied to software development to improve the productivity of project teams and quality of software. Given recent advancements and growing applications of AI and ML in practice, there will be more intelligent test automation technologies and tools that are smarter in generating test cases, test scripts, test data, and in maintaining and reusing test scripts. They would also bring advancements to formulating test scenarios, predicting application behaviors, and predicting areas and levels of test. Intelligent testing tools will need to offer smart analytics to help better diagnose faults and visualize test results and overall product quality using multi-source data.</p><h3>5. Increasing Mobile Test Automation</h3><p>The utilization of test automation in software projects is now at a low level. For mobile test automation, it is even lower. There is a current lack of right methods, tools, and devices to perform automated testing of mobile applications. The increasing shift away from desktop and web towards mobile applications along with ever shortening time-to-market requires software organizations to increase the application of test automation for mobile applications. Emerging mobile test platforms and tools such as <a href="https://kobiton.com/">Kobiton</a> and <a href="https://saucelabs.com/">Sauce Labs</a> may offer advanced and right capabilities to make mobile test automation more executable and affordable.</p><h3>6. Shortening Delivery Cycles</h3><p>Rapid changes in technologies, platforms, and devices pressure software development teams to develop, test, integrate, and deliver faster and more frequently. Software needs to be delivered and deployed daily instead of monthly or weekly. Software organizations will invest more in improving their development and delivery processes and methods as well as employing a right set of DevOps tools. This demand will derive the growth of DevOps practices and tools which leads to further utilization of test automation in QA and testing.</p><h3>7. API and Services Test Automation</h3><p>The main utilization of test automation now focuses on UI testing. A majority of API and services testing is currently performed by developers manually. The trend will be an increasing application of automating API and services testing processes, at a greater pace than automating the UI testing process. Independent testers who are equipped with intelligent and easy-to-use tools will be responsible for API and services testing, helping to reduce time-to-market while improving software quality.</p><h3>8. Integration</h3><p>To support smart testing and analytics, data has to be gathered from different sources and phases in software development, such as requirements management systems, change control systems, task management systems, and test environments. We will see test automation and management tools offering features to integrate with various ALM toolsets and test environments. This integration allows smarter decision-making concerning software testing and quality.</p><p>This article offers the bold predictions of trends in the next few years. As any prediction can be wrong, the trends here may suggest opportunities and challenges for us in the software industry.</p><p>Ref: <a href="https://dzone.com/articles/software-testing-trends-for-2018-and-beyond">dZone</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94d2514e1ab0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/software-testing-hot-cakes-for-2018-94d2514e1ab0">Software Testing Hot Cakes for 2018</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous Testing in DevOps]]></title>
            <link>https://medium.com/oceanize-geeks/continuous-testing-in-devops-76e5f638aa34?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/76e5f638aa34</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Tue, 27 Mar 2018 09:42:59 GMT</pubDate>
            <atom:updated>2018-03-27T09:45:28.774Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong><em>Testing is important to DevOps.</em></strong> Prior to code integration to trunk, developers pre-flight test their code to make sure it doesn’t blow up the trunk. During the CI cycle and code commits from multiple developers integration testing is used to verify merges. During the continuous testing phase where nightly and weekend regression runs are automated for trunk and release branches it is testing that does the job of finding problems before the software release. During the development process the verdicts trends from testing are a primary measurement of progress. During the release deployment phase more testing verifies the release packages are ready for release. Rest assured test team, you are needed. What DevOps really does is bring testing into the mainstream of development processes, and avoids the problems created by having “big-bang” testing left to the end of the cycle, such as release delays, and quality issues.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*-aabjtwmy8LTpNe9eb2OOg.png" /><figcaption>Image Source: <a href="http://blogs.thinksys.com/testing-devops-world-test-automation-sequel/">DevOps Testing</a></figcaption></figure><p><strong>Testing maturity is a key differentiator of best practices DevOps infrastructures.</strong> My experiences with DevOps infrastructures over the years indicate that testing maturity is a key differentiator of overall DevOps infrastructure maturity. Many organizations can automate their integrations, builds and delivery processes but still have trouble with the subtleness of test orchestration and automation. There is a vital role for testing architects and testing teams to offer their expertise for test design, test automation and test case development with DevOps. Whether the organization is using a test driven development methodology, behavior based test creation, model-based testing or whatever they use, testing is a vital part of the overall DevOps process — not only to ensure verify code changes work and integrate well — but to ensure the changes do not blow up the product. So clearly testing is still an integral part of product development and delivery.</p><p>Resource: <a href="https://dzone.com/articles/testing-role-in-devops">https://dzone.com/articles/testing-role-in-devops</a></p><p><strong><em>Cucumber</em></strong> is certainly one of the testing tools that fits well into DevOps. It uses a Behavior Based description approach that is well suited to applications that can be easily described. DevOps testing does not depend on any one tool or test methodology but cucumber is a good one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76e5f638aa34" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/continuous-testing-in-devops-76e5f638aa34">Continuous Testing in DevOps</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous Integration(CI) Testing]]></title>
            <link>https://medium.com/oceanize-geeks/continuous-integration-ci-testing-127e84901e7d?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/127e84901e7d</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Thu, 01 Mar 2018 06:31:23 GMT</pubDate>
            <atom:updated>2018-03-01T06:41:44.213Z</atom:updated>
            <content:encoded><![CDATA[<p>The following best practices should help you in your quest for a smoother continuous integration process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*6vL4QEj5hjDUNeUmrB8Yyw.png" /><figcaption>Continuous Integration</figcaption></figure><h3>1. Do integration testing before unit testing</h3><p>For most of us, this idea is counterintuitive. We’ve been taught that the later you discover a defect in the development cycle, the more expensive it is to fix. We try to get all the details perfected before moving on to the “big things,” like integration testing.</p><p>The problem is that that claim was rooted in the waterfall development model, in which you didn’t move to the next development until the current phase was complete. Once you move to agile development, however, the idea is no longer relevant. Agile empowers you with the flexibility to make any changes in the business logic that are necessary as you move along.</p><h3>2. Don’t test business logic with integration testing</h3><p>That’s what unit tests are for. Confusing unit tests with integration tests can have dire consequences on the time it takes to run your test suite. Unit tests are typically very fast, so they are run for every build triggered in the CI environment.</p><p>Since they target basic correctness of code, running them frequently is critical to detect bugs early on in business logic, so that the developer who introduced the bug can fix it immediately. Integration tests, on the other hand, take much longer to run, so they should not be included in every build cycle, but in something closer to a daily build.</p><h3>3. Know why integration testing is different from unit testing</h3><p>There are many telltale signs that help you easily differentiate a unit test from an integration test:</p><ul><li><strong><em>Encapsulation:</em></strong> While unit tests are well encapsulated and don’t use external resources, integration tests use additional components or infrastructures like the network, database, or file system.</li><li><strong><em>Complexity:</em></strong> Unit tests target small and distinct parts of code, so they are usually simple to write. Integration tests are more complex, often requiring tooling and setting up different infrastructures.</li><li><strong><em>Test failure:</em></strong> When a unit test fails, there is clearly a bug in the business logic of the code. When an integration test fails, you shouldn’t need to look at the code that implements business logic; the unit tests should flush out bugs at that level. It’s more likely that something has changed in the environment and needs to be addressed.</li></ul><h3>4. Keep your testing suites separate</h3><p>Integration tests should not be run together with unit tests. Developers working on specific business logic in the code must be able to run unit tests and get near-immediate feedback to ensure that they haven’t broken anything before committing code. If their test suite takes too long and they can’t afford to wait for it to finish before committing code, they are likely to just stop running tests altogether (both unit tests and integration tests). This also means that the unit tests are not properly maintained, which can eventually get you into a situation where the effort required to bring your test suite up to date with the code causes real delays in delivery.</p><p>By keeping your test suites separate, your developers can feel free to run the quick unit tests during development and before committing any code. The long and tedious integration tests should be reserved for the build server in a separate test suite, and can be run less frequently.</p><h3>5. Log extensively</h3><p>A unit test has a specific scope and tests a very small piece of your application, so when it fails, it’s usually quite easy to understand why and fix the problem. Integration tests are quite different. Their scope may span several software modules, not to mention different devices and hardware components, in any functional flow. As a result, if an integration test fails, it may be much more complex to identify the cause.</p><p>Exhaustive logging is the only way to analyze a failure, allowing you to discover where the problem lies. Still, be mindful that exhaustive logging can have a significant effect on performance, so it should be done only when needed. Make sure you use a competent logging framework that can be controlled via flags that allow for minimal logging during normal production usage and progressively more detail to be logged in the event of a problem.</p><h3>6. Don’t stop at integration testing</h3><p>Testing does not end with how your software modules work with one another, or even how they work with other, third-party modules. It goes beyond. Your software is going to be deployed in a complete production ecosystem that may include virtualization tools, databases, mail servers, load balancers, DNS servers, proxy servers, and more. Your customers’ user experience depends not only on your application, but also on how it is deployed in your production environment and how it works with all those other peripheral components. These are the components (yes, all of them) that you should be targeting, so once you have validated (or while you are validating) your high-level architecture with integration testing, make sure you also run system tests that accurately simulate your production environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=127e84901e7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/continuous-integration-ci-testing-127e84901e7d">Continuous Integration(CI) Testing</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[POPULAR SOFTWARE TESTING TOOLS]]></title>
            <link>https://medium.com/oceanize-geeks/popular-software-testing-tools-12b93265f127?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/12b93265f127</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 04:24:56 GMT</pubDate>
            <atom:updated>2018-01-30T04:32:09.807Z</atom:updated>
            <content:encoded><![CDATA[<p>New and updated tools continue to proliferate across the software testing spectrum with expanding options in testing automation, performance testing, mobile testing, niche testing, bug tracking and more. Here are 11 popular software testing tools.</p><h3><strong>1. Selenium</strong></h3><p>A testing framework for web applications on platforms like Linux, Mac and Windows, <a href="http://www.seleniumhq.org/">Selenium</a> is also used to test browser compatibility. Developers can test in a number of languages such as Java, Groovy, PHP, Ruby, C#, Python and Perl. Selenium is part of most major browsers including Firefox and Chrome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*46jMgMa0_rnpNahKwfGGEw.png" /><figcaption>Selenium</figcaption></figure><h3><strong>2. Jenkins</strong></h3><p><a href="https://jenkins.io/">Jenkins</a> is a continuous integration (CI) tool for resting code base changes in real time. It lets you detect and resolve code base problems quickly and automate build testing. An open-source program, it was forked from the Hudson project. Jenkins runs on servers in a container, and supports version control tools such as Perforce, Git and Subversion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*fiOou8ZYaZe-Ka8NUyovMw.png" /><figcaption>Jenkins</figcaption></figure><h3><strong>3. New Relic</strong></h3><p><a href="https://newrelic.com/">New Relic</a> is a SaaS product that allows you to monitor mobile and Web apps in real time. It offers deep analytics that let you get a better idea of your software performance, helping to improve user experience and overall efficiency. It sits at the cross section of customer experience data, application data and business data, giving you feedback on the software itself and how it affects business operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*Q52w2m-IOaLqNN9gDmn7tA.png" /><figcaption>New Relic</figcaption></figure><h3><strong>4. Wercker</strong></h3><p><a href="http://www.wercker.com/">Wercker</a> is a Holland-based software firm offering a continuous delivery (CD) platform that helps you build and deploy microservices and web-based applications. Based on Docker, Wercker sits between the code repository and the app. When you make a change in Git, Wercker grabs the code and puts it in a container to test it in isolation, alerting you to errors. This allows for continuous integration (CI) and rapid testing on-the-fly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*AhKfVepet58CM52-CSqKIQ.png" /><figcaption>Wercker</figcaption></figure><h3><strong>5. GitHub</strong></h3><p><a href="http://www.wercker.com/">GitHub</a> is a version control repository used by millions of developers. Many software testing tools can be linked to GitHub accounts, so reported defects are automatically recorded. For example, you might run manual tests on the testing tool while using GitHub for bug tracking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZ_-f5n45vnjrQt2G3FIyg.png" /><figcaption>GitHub</figcaption></figure><h3><strong>6. Text Shortcode</strong></h3><p><a href="https://tmux.github.io/">Tmux</a> is a popular virtual terminal multiplexer that lets you change swiftly from among several programs on the same terminal. You can separate them from one terminal and attach them to another one and use the command line interface without having to dump out of one session to start another. It is like GNU Screen but differs in that it is licensed under Berkeley Software Distribution (BSD).</p><h3><strong>7. Postman</strong></h3><p><a href="https://www.getpostman.com/">Postman</a> is a robust toolchain for API developers to share, test, document, and monitor APIs. With this tool, you may easily integrate the tests into your build automation. Postman is extremely valuable for functional testers and developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*fVBL9mtLJmHIH6YpU7WvHQ.png" /><figcaption>Postman</figcaption></figure><h3><strong>8. TestingWhiz</strong></h3><p>For automated testing of software, web apps, databases, APIs and mobile solutions, <a href="http://www.testing-whiz.com/">TestingWhiz</a> offers you codeless scripting. JavaScript and hundreds of testing commands are built in, and it integrates seamlessly with Jira, Mantis and FogBugz bug-tracking tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*fE5NuNdwtj6QlsQ8HRe3Pg.jpeg" /><figcaption>TestingWhiz</figcaption></figure><h3><strong>9. Sahi</strong></h3><p><a href="http://sahipro.com/">Sahi</a> is an open-source web application testing and automation tool. It features record and playback on all browsers, Suites and batch run, HTML playback reports and more. Written in JavaScript and Java, it first appeared on SourceForge in 2005. It works with a variety of frameworks and technologies and automates apps built using YUI, ZK, Dojo and many others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*el3zhaGRvQ5-prK1f_nPKw.png" /><figcaption>sahi</figcaption></figure><h3><strong>10. Ranorex</strong></h3><p><a href="https://www.ranorex.com/">Ranorex</a> lets you set up and run test automation scripts. It has GUI object recognition, automatic timeout handling, page object mapping built-in, dynamic web elements identification and lets you test web apps on every major web browser and platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*RRcBIEjD6a7HxGk84qlgqw.png" /><figcaption>Ranorex</figcaption></figure><h3><strong>11. HP LoadRunner, StormRunner and Performance Center</strong></h3><p>HP’s <a href="https://saas.hpe.com/en-us/software/loadrunner">LoadRunner</a> provides end-to-end system performance testing for agile and DevOps to help you identify and rectify problems before going live. Performance Center helps you plan and run tests for multiple projects. It has new open-source integrations to improve team collaboration. <a href="https://saas.hpe.com/en-us/software/stormrunner-load">StormRunner</a> Load is a SaaS load and performance testing tool designed for planning, executing and scaling mobile and web tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*CXSLqGhw1QFf3gU6xJsGIw.png" /><figcaption>LoadRunner</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12b93265f127" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/popular-software-testing-tools-12b93265f127">POPULAR SOFTWARE TESTING TOOLS</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drag and Drop Action in Selenium WebDriver]]></title>
            <link>https://medium.com/oceanize-geeks/drag-and-drop-action-in-selenium-webdriver-3fccd767ac83?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fccd767ac83</guid>
            <category><![CDATA[selenium-webdriver]]></category>
            <category><![CDATA[selenium-test-automation]]></category>
            <category><![CDATA[selenium]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Fri, 29 Dec 2017 05:26:58 GMT</pubDate>
            <atom:updated>2017-12-29T05:44:47.807Z</atom:updated>
            <content:encoded><![CDATA[<p>We have predefined method called <strong>dragAndDrop(source, destination)</strong> which is a method of Actions class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*sw2FPqCFcyPcUO1QGRfJ6w.png" /><figcaption>Selenium</figcaption></figure><p>Approach- Find the xpath of the Source and find the xpath of destination.</p><p>Both source and destination in form of WebElement.</p><p><em>Note- Any method of Actions class we need to call perform () method otherwise we will get an exception. If we have series of action in our script using Actions class then we have to call build().perform() method.</em></p><p><strong>publicclass</strong>DragDrop {</p><p><strong>public static </strong>WebDriver driver=<strong>new </strong>FirefoxDriver();</p><p><strong>public</strong> String baseurl=”http://www.abcxyz.html&quot;;</p><p><strong>public void </strong>open_url()</p><p>{</p><p>driver.get(baseurl);</p><p>driver.manage().window().maximize();</p><p>}</p><p><strong>public void</strong> action_1() <strong>throws </strong>InterruptedException</p><p>{</p><p>Thread.sleep(500);</p><p>driver.manage().timeouts().implicitlyWait(2000, TimeUnit.SECONDS);</p><p>driver.findElement(By.xpath(“.//*[@id=’box1&#39;]”)).click();</p><p>WebElement drag=driver.findElement(By.xpath(“.//*[@id=’box1&#39;]”));</p><p>WebElement drop =driver.findElement(By.xpath(“.//*[@id=’box101&#39;]”));</p><p>Actions builder= <strong>new</strong>Actions(driver);</p><p>builder.dragAndDrop(drag, drop).perform();</p><p>builder.build();</p><p>}</p><p><strong>public void</strong> action_2() <strong>throws </strong>InterruptedException</p><p>{</p><p>Thread.sleep(500);</p><p>driver.manage().timeouts().implicitlyWait(2000, TimeUnit.SECONDS);</p><p>driver.findElement(By.xpath(“.//*[@id=’box4&#39;]”)).click();</p><p>WebElement drag=driver.findElement(By.xpath(“.//*[@id=’box4&#39;]”));</p><p>WebElement drop =driver.findElement(By.xpath(“.//*[@id=’box104&#39;]”));</p><p>Actions builder= <strong>new</strong>Actions(driver);</p><p>builder.dragAndDrop(drag, drop).perform();</p><p>builder.build();</p><p>}</p><p><strong>public void</strong> action_3() <strong>throws </strong>InterruptedException</p><p>{</p><p>Thread.sleep(500);</p><p>driver.manage().timeouts().implicitlyWait(2000, TimeUnit.SECONDS);</p><p>driver.findElement(By.xpath(“.//*[@id=’box2&#39;]”)).click();</p><p>WebElement drag=driver.findElement(By.xpath(“.//*[@id=’box2&#39;]”));</p><p>WebElement drop =driver.findElement(By.xpath(“.//*[@id=’box102&#39;]”));</p><p>Actions builder= <strong>new</strong>Actions(driver);</p><p>builder.dragAndDrop(drag, drop).perform();</p><p>builder.build();</p><p>}</p><p><strong>public void</strong> action_4() <strong>throws </strong>InterruptedException</p><p>{</p><p>Thread.sleep(500);</p><p>driver.manage().timeouts().implicitlyWait(2000, TimeUnit.SECONDS);</p><p>driver.findElement(By.xpath(“.//*[@id=’box3&#39;]”)).click();</p><p>WebElement drag=driver.findElement(By.xpath(“.//*[@id=’box3&#39;]”));</p><p>WebElement drop =driver.findElement(By.xpath(“.//*[@id=’box103&#39;]”));</p><p>Actions builder= <strong>new</strong>Actions(driver);</p><p>builder.dragAndDrop(drag, drop).perform();</p><p>builder.build();</p><p>}</p><p><strong>public void</strong> action_5() <strong>throws </strong>InterruptedException</p><p>{</p><p>Thread.sleep(500);</p><p>driver.manage().timeouts().implicitlyWait(2000, TimeUnit.SECONDS);</p><p>driver.findElement(By.xpath(“.//*[@id=’box5&#39;]”)).click();</p><p>WebElement drag=driver.findElement(By.xpath(“.//*[@id=’box5&#39;]”));</p><p>WebElement drop =driver.findElement(By.xpath(“.//*[@id=’box105&#39;]”));</p><p>Actions builder= <strong>new</strong>Actions(driver);</p><p>builder.dragAndDrop(drag, drop).perform();</p><p>builder.build();</p><p>}</p><p><strong>public void</strong> action_6() <strong>throws </strong>InterruptedException</p><p>{</p><p>Thread.sleep(500);</p><p>driver.manage().timeouts().implicitlyWait(2000, TimeUnit.SECONDS);</p><p>driver.findElement(By.xpath(“.//*[@id=’box7&#39;]”)).click();</p><p>WebElement drag=driver.findElement(By.xpath(“.//*[@id=’box7&#39;]”));</p><p>WebElement drop =driver.findElement(By.xpath(“.//*[@id=’box107&#39;]”));</p><p>Actions builder= <strong>new</strong>Actions(driver);</p><p>builder.dragAndDrop(drag, drop).perform();</p><p>builder.build();</p><p>}</p><p><strong>public void</strong> action_7() <strong>throws </strong>InterruptedException</p><p>{</p><p>Thread.sleep(500);</p><p>driver.manage().timeouts().implicitlyWait(5000, TimeUnit.SECONDS);</p><p>driver.findElement(By.xpath(“.//*[@id=’box6&#39;]”)).click();</p><p>WebElement drag=driver.findElement(By.xpath(“.//*[@id=’box6&#39;]”));</p><p>WebElement drop =driver.findElement(By.xpath(“.//*[@id=’box106&#39;]”));</p><p>Actions builder= <strong>new</strong>Actions(driver);</p><p>builder.dragAndDrop(drag, drop).perform();</p><p>builder.build();</p><p>}</p><p><strong>public static void</strong> main(String[] args) <strong>throws </strong>InterruptedException {</p><p>DragDrop test=<strong>new </strong>DragDrop();</p><p>test.open_url();</p><p>test.action_1();</p><p>test.action_2();</p><p>test.action_3();</p><p>test.action_4();</p><p>test.action_5();</p><p>test.action_6();</p><p>test.action_7();</p><p>driver.close();</p><p>}</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fccd767ac83" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/drag-and-drop-action-in-selenium-webdriver-3fccd767ac83">Drag and Drop Action in Selenium WebDriver</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous Performance Testing]]></title>
            <link>https://medium.com/oceanize-geeks/continuous-performance-testing-4968fdaf5c63?source=rss-8747f953f5d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4968fdaf5c63</guid>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Muntasir Abdullah Mizan]]></dc:creator>
            <pubDate>Thu, 30 Nov 2017 06:09:06 GMT</pubDate>
            <atom:updated>2017-11-30T06:17:57.353Z</atom:updated>
            <content:encoded><![CDATA[<p>Nothing upsets engineering teams more than frantic application troubleshooting and patching in the middle of the night. And absolutely nothing upsets business people and destroys careers more than watching customers switch to your competition during the year’s heaviest sales days because their website or mobile application is visibly faster. Continuous Performance Testing can help prevent these problems by catching them during the development process instead of after an application is in production.</p><ul><li>2012: Research showed that Amazon would lose $1.6 billion in sales every year <a href="http://www.fastcompany.com/1825005/how-one-second-could-cost-amazon-16-billion-sales">if its site took one more second to load.</a></li><li>2013: 39% of e-retailers claimed they <a href="http://www.slideshare.net/LoadImpact/state-of-web-readiness-eco-2013">lost money last year due to performance or stability problems.</a></li><li>2014: The web performance monitoring company Catchpoint Systems looked at aggregate performance on Black Friday and compared it to the same timeframe in 2013. <a href="http://venturebeat.com/2014/11/30/black-friday-2014-e-commerce-desktop-pages-were-20-slower-than-in-2013-mobile-pages-were-57-slower/">The results are notable</a>: desktop web pages were 19.85 percent slower, while mobile web pages were a whopping 57.21 percent slower.</li><li>2015: Some major e-retailers’ sites <a href="https://www.internetretailer.com/2015/11/30/heavy-cyber-monday-traffic-downs-targetcom-and-slows-paypal">buckled under the pressure of heavy holiday traffic</a> during 2015’s Cyber Monday peak traffic times.</li></ul><p>Continuous Performance Testing is gaining increased attention and support from the developer and vendor communities. The core idea is simple and straightforward: as developers routinely and continuously develop new features and make changes to an application, wouldn’t it be great to know, immediately and precisely, what kind of impact each change would have on the application’s performance?</p><p>In order to do that, the new application build has to be tested for performance under stress — after the build process is complete, but before the build is released to production. Since most development teams already have a functioning CI process, performance testing simply becomes a step in the CI pipeline — usually performed after regression testing but before production deployment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*KfKfmHFNZsQgVXL4yR42Kg.png" /></figure><p>The goals of continuous performance testing can be broadly classified in four categories:</p><ol><li><strong>Certify that the application meets performance targets.</strong></li></ol><p>Performance testing objectives must correlate to business needs and represent real-world business scenarios concerning real customers. Start with input from the business side: what transaction volume and response latency is required to support the immediate business? What scenarios are most critical: checking out many small orders simultaneously or processing a relatively modest number of “big baskets” containing dozens of items? Each company has different critical performance constraints. These KPIs must be met by every production release, and therefore must be codified as the top priority in all test cases.</p><p><strong>2. Plan capacity and manage growth</strong></p><p>Even excellent performance from the applications you currently have in production won’t necessarily protect you from crashes if the number of customers, requests or data sets suddenly increase. Preparation for growth is a serious challenge. Performance testing helps build a capacity planning model and gives you a chance to update your production environment before a demand surge causes a major problem.</p><p><strong>3. Track useful performance metrics</strong></p><p>All too often, business users only receive ‘green’ reports that tell them performance is good or panic reports about catastrophic failures, with nothing in between. A well-designed performance testing strategy can include many key metrics so business users can see trends and prepare for them. These metrics could be related to user experience, capacity and business areas (e.g. response time, maximum throughput, resources utilization, etc.).</p><p><strong>4. Identify load-related weaknesses</strong></p><p>Solid knowledge of your weak points and of load factors that can break your digital services is essential to develop upgrade plans and backup plans. A system-wide capacity upgrade well ahead of the demand is often neither practical, nor the only way to manage performance risks. However, the knowledge of your risks and exposures is a critical element of sensible risk management strategies. Performance stress testing is how you discover these areas and provide all necessary information in advance to make informed risk management decisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4968fdaf5c63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oceanize-geeks/continuous-performance-testing-4968fdaf5c63">Continuous Performance Testing</a> was originally published in <a href="https://medium.com/oceanize-geeks">Oceanize Lab Geeks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>