<?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 Masum Rahman on Medium]]></title>
        <description><![CDATA[Stories by Masum Rahman on Medium]]></description>
        <link>https://medium.com/@masumrahman73?source=rss-bdd147de91f1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zuXj8DmNz4K3eQNQ</url>
            <title>Stories by Masum Rahman on Medium</title>
            <link>https://medium.com/@masumrahman73?source=rss-bdd147de91f1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:52:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@masumrahman73/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[Top SQA skills that you must have in Bangladesh in order to get a Job!]]></title>
            <link>https://masumrahman73.medium.com/top-sqa-skills-that-you-must-have-in-bangladesh-in-order-to-get-a-job-23f964a33515?source=rss-bdd147de91f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/23f964a33515</guid>
            <category><![CDATA[skills-development]]></category>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[engineer]]></category>
            <dc:creator><![CDATA[Masum Rahman]]></dc:creator>
            <pubDate>Sun, 25 Oct 2020 19:23:03 GMT</pubDate>
            <atom:updated>2020-10-25T19:23:03.852Z</atom:updated>
            <content:encoded><![CDATA[<p>I have gone through some SQA job requirements from multiple IT companies that are published in different sources such as Facebook groups, bdjobs, LinkedIn and collect some typical requirements that most companies are looking for in the role of a Software Quality Assurance Engineer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AjI-6OHQ_MHw1XGfOEvPtg.jpeg" /></figure><p><em>I’ll be dividing this into 3 sections which are <br> → Freshers ( 0 to 1 years of experience ) <br> → Juniors ( 1 to 2 years of experience )<br> → Seniors ( 2 to 3 years of experience )</em></p><p><strong>For Freshers: </strong><em>Companies expect from a fresher that he should have these skills / responsibilities which are mentioned below.</em></p><p>· Solid knowledge about Software Development Life Cycle &amp; Software Testing Life Cycle.<br> · Review and Understand Product and Business Requirements.<br> · Write Manual and Automation Test Cases and Test Documentations.<br> · Create comprehensive and structured Test Plans and Test Scenarios.<br> · Estimate, Prioritize, Execute, Plan with the team and coordinate Testing Activities.<br> · Identify, Record and Track Bugs.<br> · Should have sound knowledge about Jira &amp; Bug Tracking Tools.<br> · Perform a variety of tests, such as UI, Regression, Performance, Security, Stability Testing to confirm the stability of software systems.<br> · Knowledge of SQL.<br> · Design, develop and execute automation scripts using open source tools such as Selenium, JMeter.</p><p><strong>For Juniors: </strong><em>Companies expect from a 1 to 2 years of experienced person should have these skills / responsibilities which are mentioned below.</em></p><p>· Create and execute test cases for assigned feature(s)- <br> Plan and write manual test cases while Dev Team begins coding work.<br> · Conduct testing as code is completed and merged to testing environment.<br> · Report any bugs<br> · Retest until all test cases are passing as expected<br> · Conduct necessary regression testing<br> · Evaluate and update test run results<br> · Keep manual test cases up to date as things inevitably change.<br> · Update/retire any manual test cases that have been become obsolete<br> · Communicate issues, risks and test status in a timely and detailed manner<br> · Ability to troubleshoot software defects and identify root cause<br> · Assist in creating and maintaining documentation<br> · Expand the QA capabilities, quality and efficiency<br> · Evaluate business requirement and technical specification documents to craft test strategies<br> · Level of Effort (LOE) assessments which would account for, durations, constraints, assumptions, etc. that are needed to fulfill test objectives<br> · Should have good knowledge on different Automation test tools and frameworks. i.e Appium, TestNG, Maven, Junit, Selenium, Apache Jmeter, Postman.</p><p><strong>For Seniors: </strong><em>Companies expect from a 2 to 3 years of experienced person should have these skills / responsibilities which are mentioned below.</em></p><p>· Strong knowledge of software QA methodologies, tools and processes<br> · Understanding of programming for the web and basic web security<br> · Basic understanding of programming and hands on knowledge in programming language like Java/Python<br> · Have strong SQA technical skills, both functional and non-functional, manual and automation, ideally in a continuous delivery environment.<br> · Skill in SQA of Web Application, API testing, Smartphone application etc<br> · Conduct automated and manual tests to ensure deliverables fit the requirements.<br> · Solid knowledge of SQL Scripting<br> · Hand on experience in project testing using Jira, Blackbox, Whitebox, Selenium, Robot Framework, TestNG, AutoIT, RESTful APIs.<br> · Understand the client’s requirements and determine the testing scope.<br> · Prepare a detailed, comprehensive and well-structured, all sorts of test documents (test plan, test report, release notes, test cases, checklists, traceability matrix etc. as per requirements.)<br> · Determine and define test strategies for all sorts of applications.<br> · Breakdown tasks into major test areas and estimate the time.<br> · Execute tests or write test code to verify enhancements and bug fixes<br> · Report bugs/defects with appropriate details.<br> · Retrieve the latest code from the appropriate branch.<br> · Submit changes to the appropriate branch with comments.<br> · View the repository log and understand where any specific modification has been made.<br> · Merge source code changes made by other team members.<br> · Perform R&amp;D to identify the scope of test ideas that may scale up the output level<br> · Review all sorts of tasks of team members.<br> · Communicate with Dev lead/ manager to improve development processes and resolve problems.<br> · Should have people skills to foster effective communication among team members and to motivate them<br> · Ability to understand the strengths and weaknesses of teammates in order to work with them constructively.<br> · Results-oriented R&amp;D skills and proactive attitude<br> · Ability to visualize real-time business situations and scenarios.<br> · Excellent written and verbal communication skills.<br> · Professional Certification in SQA like ISTQB is a bonus</p><p>If anyone wishes to train themselves according to the experience he/she had, then I believe, this content would be very helpful. Although these are not fixed skills that one should have, so build up these skills immediately, it’s more like a common skill that you need to become a master in this area.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23f964a33515" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Common Test Scenarios of Mobile Testing]]></title>
            <link>https://masumrahman73.medium.com/common-test-scenarios-of-mobile-testing-3ce1af107bdb?source=rss-bdd147de91f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ce1af107bdb</guid>
            <category><![CDATA[testing-tools]]></category>
            <category><![CDATA[test-scenarios]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[test-case]]></category>
            <category><![CDATA[mobile-testing]]></category>
            <dc:creator><![CDATA[Masum Rahman]]></dc:creator>
            <pubDate>Sun, 20 Sep 2020 04:30:27 GMT</pubDate>
            <atom:updated>2020-09-20T04:44:03.139Z</atom:updated>
            <content:encoded><![CDATA[<p>Providing a collection of common Functional, Performance, Security, Usability, Compatibility, Recoverability test cases/test scenarios for mobile testing along with some testing tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DA8XXr4MH7qn-cDOBUzKCA.jpeg" /></figure><h3>Functional Testing Test Cases</h3><p>In mobile testing functional testing generally deals with testing the user interactions and the transactions.</p><p>The most fundamental test scenarios in functional testing can be considered as :</p><p>1. To validate whether all the required mandatory fields are working as required.</p><p>2. To validate that the mandatory fields are displayed on the screen in a distinctive way than the non-mandatory fields.</p><p>3. To validate whether the application works as per as required whenever the application starts/stops.</p><p>4. To validate whether the application goes into minimized mode whenever there is an incoming phone call. In order to validate the same, we need to use a second phone, to call the device.</p><p>5. To validate whether the phone is able to store, process, and receive SMS whenever the app is running. In order to validate the same, we need to use a second phone to send SMS to the device which is being tested and where the application under test is currently running.</p><p>6. To validate that the device is able to perform required multitasking requirements whenever it is necessary to do so.</p><p>7. To validate that the application allows necessary social network options such as sharing, posting, and navigation, etc.</p><p>8. To validate that the application supports any payment gateway transaction such as Visa, Mastercard, Paypal, etc as required by the application.</p><p>9. To validate that the page scrolling scenarios are being enabled in the application as necessary.</p><p>10. To validate that the user receives an appropriate error message like “Network error. Please try after some time” whenever there is any network error.</p><p>11.To validate whether the application performs according to the requirement in all versions of Mobile that is 2g, 3g, and 4g.</p><p>12. To perform Regression Testing to uncover new software bugs in existing areas of a system after changes have been made to them. Also rerun previously performed tests to determine that the program behavior has not changed due to the changes.</p><p>13. To validate whether the application provides an available user guide for those who are not familiar with the app.</p><h3><strong>Performance Testing Test Cases</strong></h3><p>Performance testing for the mobile application ensures that your application performs as required under certain performance requirements like a number of users, memory requirements, etc.</p><p>The general test scenarios for Performance Testing in a Mobile application are:</p><p>1. To determine whether the application performs as per the requirement under different load conditions.</p><p>2. To determine whether the current network coverage is able to support the application at peak, average, and minimum user levels.</p><p>3. To determine whether the existing client-server configuration setup provides the required optimum performance level.</p><p>4. To validate whether the response time of the application is as per the requirements.</p><p>5. To evaluate whether the battery life can support the application to perform under projected load volumes.</p><p>6. To validate application performance when the network is changed to WIFI from 2G/3G or vice versa.</p><p>7. To validate that the battery consumption, memory leaks, resources like GPS, Camera performance is well within required guidelines.</p><p>8. To validate the application longevity whenever the user load is rigorous.</p><p>9. To validate the network performance while moving around with the device.</p><p>10. To validate each of the required CPU cycle is optimization.</p><h3><strong>Security Testing Test Cases</strong></h3><p>In times of increasing cyber-crime, security testing is very important. It checks whether your application fulfills all the security requirements.</p><p>Below are some of the most important security testing test cases for mobile apps that can ensure better security of your application:</p><p>1. To validate that the application is able to withstand any brute force attack which is an automated process of trial and error used to guess a person’s username, password, or credit card number.</p><p>2. To validate whether an application is not permitting an attacker to access sensitive content or functionality without proper authentication.</p><p>3. To validate that the application has a strong password protection system and it does not permit an attacker to obtain, change, or recover another user’s password.</p><p>4. To validate that the application does not suffer from insufficient session expiration.</p><p>5. To prevent SQL injection related attacks.</p><p>6. To protect the application and the network from the denial of service attacks.</p><p>7. To validate whether the business logic implementation is secured and not vulnerable to any attack from outside.</p><p>8. To analyze file system interactions, determine any vulnerability, and correct these problems.</p><p>9. To validate the protocol handlers for example trying to reconfigure the default landing page for the application using a malicious iframe.</p><p>10. To protect against malicious client-side injections.</p><p>11.To protect against malicious runtime injections.</p><p>12. To investigate cookies and preventing any malicious deeds from the cookies.</p><p>13. To provide regular audits for data protection analysis.</p><p>14. Investigate custom created files and preventing any malicious deeds from the custom created files.</p><p>15. To prevent buffer overflows and memory corruption cases.</p><h3><strong>Usability Testing Test Cases</strong></h3><p>The usability testing tests whether your mobile application is easy for the users to use. The main objective of usability testing is to whether your application supports intuitive, easy-to-use, and industry-accepted interfaces.</p><p>The following are the most prominent areas for usability testing:</p><p>1. To ensure that the buttons should have the required size and be suitable for big fingers.</p><p>2. To ensure that the buttons are placed in the same section of the screen to avoid confusion to the end-users.</p><p>3. To ensure that the icons are natural and consistent with the application.</p><p>4. To ensure that the buttons, which have the same function should also have the same color.</p><p>5. To ensure that the validation for the tapping zoom-in and zoom-out facilities should be enabled.</p><p>6. To ensure that the keyboard input can be minimized in an appropriate manner.</p><p>7. To ensure that the application provides a method for going back or undoing an action, on touching the wrong item, within an acceptable duration.</p><p>8. To ensure that the contextual menus are not overloaded because it has to be used quickly.</p><p>9. To ensure that the text is kept simple and clear to be visible to the users.</p><p>10. To ensure that the short sentences and paragraphs are readable to the end-users.</p><p>11.To ensure that the font size is big enough to be readable and not too big or too small.</p><p>12. To validate the application prompts the user whenever the user starts downloading a large amount of data which may be not conducive for the application performance.</p><p>13. To validate that the closing of the application is performed from different states and verify if it re-opens in the same state.</p><p>14. To ensure that all strings are converted into appropriate languages whenever a language translation facility is available.</p><p>15. To ensure that the application items are always synchronized according to the user actions.</p><p>16. To ensure that the end-user is provided with a user manual which helps the end-user to understand and operate the application who may be not familiar with the application’s proceedings.</p><h3><strong>Compatibility Testing Test Cases</strong></h3><p>Compatibility testing is very important as markets are flooded with various kinds of mobile devices. Your application should be compatible with all these devices to reach wider customers. Compatibility tests your application compatibility with various mobile devices, OS, and a combination of both.</p><p>Some of the prominent test cases for compatibility testing are:</p><p>1. To validate that the user Interface of the application is as per the screen size of the device, no text/control is partially invisible or inaccessible.</p><p>2. To ensure that the text is readable for all users for the application.</p><p>3. To ensure that the call/alarm functionality is enabled whenever the application is running. The application is minimized or suspended on the event of a call and then whenever the call stops the application is resumed.</p><h3><strong>Recoverability Testing Test Cases</strong></h3><p>1. Crash recovery and transaction interruptions</p><p>2. Validation of the effective application recovery situation post unexpected interruption/crash scenarios.</p><p>3. Verification of how the application handles a transaction during a power failure (i.e. Battery dies or sudden manual shutdown of the device)</p><h3><strong>What Tools are Used in Mobile Automation Testing?</strong></h3><p>· Appium</p><p>· Robot Framework</p><p>· TestComplete</p><p>· Robitium</p><p>· Monkey Runner</p><p>· Testingbot</p><p>· Experitest</p><h3><strong>Additional Open-source Mobile Responsive Test Tools:</strong></h3><p><strong>#1) Websiteresponsivetest.com: </strong>This tool supports all the major web browsers and it provides a preview of how the actual website will look like. To get the results of the responsiveness of a website, we have to enter the URL of our website.</p><p><strong>#2) Screenfly: </strong>It is also a mobile responsive testing tool and can be used for testing on the Galaxy tab, iPad, etc. It automatically detects the mobile site of the website and takes you to the same.</p><p><strong>#3) VeiwPort Resizer: </strong>It is a configurable tool and can be used to customize the screen size of a browser.</p><p><strong>#4) Responsinator: </strong>This comes as a paid version also where you can buy the sub-domain for your testing. By providing the URL of the website, this tool shows how the website will look like.</p><h3><strong>Conclusion</strong></h3><p>Mobile responsive testing is very important to ensure if all the users get an optimal viewing experience on their devices, maybe a laptop, a desktop, a tablet, or a smartphone. You may execute some or all Test Cases based on your mobile testing requirements. Test Cases are organized based on Mobile Testing Types.</p><h4><strong>References</strong></h4><p>1. <a href="https://www.guru99.com/testing-mobile-apps.html">https://www.guru99.com/testing-mobile-apps.html</a></p><p>2. <a href="https://www.testbytes.net/blog/test-cases-for-mobile-applications/">https://www.testbytes.net/blog/test-cases-for-mobile-applications/</a></p><p>3. <a href="https://www.softwaretestinghelp.com/mobile-responsive-test/">https://www.softwaretestinghelp.com/mobile-responsive-test/</a></p><p>4. <a href="https://www.testrigtechnologies.com/25-test-scenarios-for-mobile-app-testing/">https://www.testrigtechnologies.com/25-test-scenarios-for-mobile-app-testing/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ce1af107bdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>