Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the stratum domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultimate-member domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the um-recaptcha domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-maximum-upload-file-size domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-optimize domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the iksm domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultimate-addons-for-gutenberg domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114
Ashish Kumar – Page 29 – SoliteraTA

SoliteraTA

Author name: Ashish Kumar

Ashish

click on desktop window element {string} for {string} times

Desktop step-Definition click on desktop window element {string} for {string} times Keyword Given, When, And, Then Description Will click on the desktop window element multiple times Declaration Remarks Code Element Application Test Data When click on desktop window element “InputField” for “5” times ” InputField ID Input ” NILL NILL This step performs a click action on the element specified by “element_name” for multiple times within the desktop window. Restriction Element and application file should be in xml format. Ensure that “element_name” is a valid and unique identifier for the element you want to double-click on. Make sure the element is visible and clickable before attempting the double-click action. Table of contents Keyword Description Declaration Remarks Restriction

click on desktop window element {string} for {string} times Read More »

press {string} keys on desktop element {string}

Desktop step-Definition press {string} keys on desktop element {string} Keyword Given, When, And, Then Description Will press the key on element Declaration Code Element Application Test Data When press “ENTER” keys on desktop element “InputField” ” InputField ID Input ” NILL NILL Remarks The Windows Application Driver (WinAppDriver) installed on your machine. You can download it from the  WinAppDriver v1.2.1. A windows machine with the desktop application you want to test installed. Inspect.exe should be present on your system to inspect the element of desktop application under test (Inspect .exe is a part of Microsoft SDK). Default winAppDriver location: C:Program Files (x86)Windows Application Driver Restriction Element and application file should be in xml format. Table of contents Keyword Description Declaration Remarks Restriction

press {string} keys on desktop element {string} Read More »

right click on the desktop element {string}

Desktop step-Definition right click on the desktop element {string} Keyword Given, When, And, Then Description Will right click on the desktop element Declaration Code Element Application Test Data When right click on the desktop element “InputField” ” InputField ID Input ” NILL NILL Remarks This step performs a right click action on the element specified by “element_name” within the desktop window. Restriction Element and application file should be in xml format. Ensure that “element_name” is a valid and unique identifier for the element you want to right click on. Make sure the element is visible and clickable before attempting the right click action. Table of contents Keyword Description Declaration Remarks Restriction

right click on the desktop element {string} Read More »

How to Write Effective Automation Test Cases

How to Write Effective Automation Test Cases Automation testing is the process of using software to perform repetitive tasks that would otherwise be done manually. This can save time and money, as well as improve the quality of software. One of the most important aspects of automation testing is writing effective test cases. A well-written test case will ensure that your automation tests are comprehensive, accurate, and easy to maintain. Here are some tips for writing effective automation test cases: Start with the business requirementsWhat are the key features and functions of your software? What are the critical business scenarios that you need to test? Once you understand the business requirements, you can start to write test cases that address them. Identify the different types of test cases you need to writeThere are many different types of automation test cases, such as unit tests, integration tests, system tests, and acceptance tests. Each type of test case has a different purpose, so you need to identify the right types of test cases for your specific needs. Write clear and concise test stepsEach test step should be clear and concise, and it should be easy to understand what you are trying to test. Avoid using jargon or technical terms that your readers may not understand. Use a consistent naming convention for your test cases and test stepsThis will make it easier to find and understand your test cases. Use data-driven testing whenever possibleData-driven testing allows you to test your software with different sets of data. This can help you to increase the coverage of your tests and to identify bugs that you might not have found otherwise. Use a test management tool to track your test casesA test management tool can help you to keep track of your test cases, to assign test cases to testers, and to track the progress of your testing. Automate your test cases as much as possibleAutomation can save you time and money, and it can also help you to improve the quality of your tests. Document your test casesThis will make it easier to understand and maintain your test cases. Review your test cases regularlyThis will help you to identify any gaps or outdated test cases. Continuously improve your test casesAs you learn more about your software, you may need to update your test cases to reflect the changes. By following these tips, you can write effective automation test cases that will help you to improve the quality of your software. Additional tips to write test cases In addition to the tips mentioned above, here are some additional things to keep in mind when writing automation test cases: Use a tool that supports the type of automation testing you want to do. Write your test cases in a way that is easy to understand and maintain. Use a consistent naming convention for your test cases and test steps. Use data-driven testing whenever possible. Automate your test cases as much as possible. Document your test cases. Review your test cases regularly. Continuously improve your test cases. By following these tips, you can write effective automation test cases that will help you to improve the quality of your software. As an example, SoliteraTA (a test automation tool) that supports Gherkin-based step definitions for writing test scripts. Gherkin is a language that is used to write plain language specifications of software behavior. This makes it easy to write and understand test scripts, and it also makes it easier to collaborate with other testers. Related posts How to Choose the Right Test Automation Tool for Your Testing Needs Read More 10 Automation Testing Best Practices That Will Save You Time and Money Read More

How to Write Effective Automation Test Cases Read More »

10 Automation Testing Best Practices That Will Save You Time and Money

10 Automation Testing Best Practices That Will Save You Time and Money Automation testing is the process of using software to perform repetitive tasks that would otherwise be done manually. This can save time and money, as well as improve the quality of software. There are many different automation testing best practices that can be implemented to achieve these benefits. Here are 10 of the most important: Start early and automate oftenThe earlier you start automating your tests, the more time and money you will save in the long run. Automation can be used to test even the smallest changes to your software, so it is important to start automating as soon as possible. Choose the right tool for the jobThere are many different automation testing tools available, so it is important to choose the right one for your needs. Some factors to consider include the type of software you are testing, the number of tests you need to automate, and your budget. Write reusable test casesWhen you write test cases, make sure they are reusable. This means that they should be written in a way that they can be used to test multiple variations of your software. Reusable test cases will save you time in the long run, as you will not need to rewrite them every time you make a change to your software. Use data-driven testingData-driven testing is a technique that allows you to use different sets of data to drive your tests. This can be useful for testing different scenarios or for testing different users. Data-driven testing can save you time and effort, as you do not need to write multiple test cases for each scenario. Automate regression testingRegression testing is the process of testing your software after you have made changes to it. Automation can be used to automate regression testing, which can save you a lot of time. Use a continuous integration/continuous delivery (CI/CD) pipelineA CI/CD pipeline is a set of automated processes that help you to build, test, and deploy your software. Automation can be used to automate your CI/CD pipeline, which can help you to release your software more quickly and reliably. Test on a variety of devices and browsersYour software should be tested on a variety of devices and browsers to ensure that it works properly on all platforms. Automation can be used to automate this testing, which can save you a lot of time. Use a test management toolA test management tool can help you to manage your automation testing projects. This can include features such as test case tracking, defect tracking, and reporting. A test management tool can help you to save time and improve the efficiency of your automation testing process. Document your automation testsIt is important to document your automation tests so that you can easily understand and maintain them. Documentation can also help you to share your tests with other team members. Continuously improve your automation testing processAutomation testing is an evolving field, and there are always new tools and techniques being developed. It is important to continuously improve your automation testing process to ensure that you are using the latest best practices. By following these best practices, you can save time and money while improving the quality of your software. Related posts How to Choose the Right Test Automation Tool for Your Testing Needs Read More How to Write Effective Automation Test Cases Read More

10 Automation Testing Best Practices That Will Save You Time and Money Read More »

verify app “<testdata_name>” is installed on the mobile device

Mobile Step Definition verify app “<testdata_name>” is installed on the mobile device Keyword Given, When, And, Then Description Will verify given app installed using the app package name Declaration Code Element Application Test Data Then verify app “” is installed on the mobile device NILL NILL A AppName Cricbuzz Remarks  The “<testdata_name>” that is used through test data file should be in angular brackets Restriction               NILL Table of contents Keyword Description Declaration Remarks Restriction

verify app “<testdata_name>” is installed on the mobile device Read More »

enter text “<testdata_name>” in mobile input field “element_name”

Mobile Step Definition enter text “<testdata_name>” in mobile input field “element_name” Keyword Given, When, And, Then Description Will enter text in the given input field Declaration Code Element Application Test Data Then enter text “” in mobile input field “SearchButton” SearchButton XPATH //android.widget.ImageView[@content-desc=”Search”] NILL A Text1 SoliteraTA Remarks The “<testdata_name>” that is used through test data file should be in angular brackets The “element_name” that is used through element data file should be in double quotes. Restriction “element_name” should be corresponds to a valid dropdown in the application. Table of contents Keyword Description Declaration Remarks Restriction

enter text “<testdata_name>” in mobile input field “element_name” Read More »

verify “<testdata_name>” text at “element_name” input location in mobile screen

Mobile Step Definition verify “<testdata_name>” text at “element_name” input location in mobile screen Keyword Given, When, And, Then Description Will verify text at the input field Declaration Code Element Application Test Data Then verify “” text at “SearchButton” input location in mobile screen SearchButton XPATH //android.widget.ImageView[@content-desc=”Search”] NILL A Text1 SoliteraTA Remarks The “<testdata_name>” that is used through test data file should be in angular brackets  The “element_name” that is used through element data file should be in double quotes. Restriction “element_name” should be corresponds to a valid element in the application. Table of contents Keyword Description Declaration Remarks Restriction

verify “<testdata_name>” text at “element_name” input location in mobile screen Read More »

verify “<testdata_name>” text at “element_name” non-input location in mobile screen

Mobile Step Definition verify “<testdata_name>” text at “element_name” non-input location in mobile screen Keyword Given, When, And, Then Description Will verify text at the non-input field Declaration Code Element Application Test Data Then verify “” text at “SearchButton” non-input location in mobile screen SearchButton XPATH //android.widget.ImageView[@content-desc=”Search”] NILL A Text1 SoliteraTA Remarks The “<testdata_name>” that is used through test data file should be in angular brackets  The “element_name” that is used through element data file should be in double quotes. Restriction “element_name” should be corresponds to a valid element in the application. Table of contents Keyword Description Declaration Remarks Restriction

verify “<testdata_name>” text at “element_name” non-input location in mobile screen Read More »

click on checkbox in mobile screen “element_name”

Mobile Step Definition click on checkbox in mobile screen “element_name” Keyword Given, When, And, Then Description Will select the checkbox Declaration Code Element Application Test Data Then click on checkbox in mobile screen “SearchButton” SearchButton XPATH //android.widget.ImageView[@content-desc=”Search”] NILL NILL Remarks The “element_name” that is used through element data file should be in double quotes. Restriction “element_name” should be corresponds to a valid checkbox in the application. Table of contents Keyword Description Declaration Remarks Restriction

click on checkbox in mobile screen “element_name” Read More »

Solitera may collect certain information by automated means, such as cookies and web beacons, when a user visits our website. A “cookie” is a small piece of data that a website can send to your browser, which may then be stored on your system. learn more