Test Automation Prerequisites

This article outlines the prerequisites for test automation in the context of PriceFx Unity. It covers the basic knowledge required for using PriceFx Unity, as well as the tools needed for test automation, including an IDE tool, Git, Node.js, and a package manager.

PriceFx Unity is a platform that provides pricing management solutions. It is important for test automation because it allows automation of testing processes related to pricing management, which can help ensure the accuracy and efficiency of pricing strategies and calculations.

PriceFx Unity Knowledge

Having a basic understanding of the PriceFx application is beneficial for starting with test automation. Everyone should understand Unity’s common functionality of its shared features or functions available across different parts of the application. Additionally, knowledge of Unity’s application modules (ie. Price Setting, Quoting, etc.) and understanding each of their aspects is important for effectively automating tests related to the PriceFx solution.

As a foundation for starting with the test automation, it would be good to have some basic knowledge of PriceFx application.

Test Automation Tools

Before using test automation, there are some the tools required for using Cypress, a popular test automation framework. Here are the tools needed and their purposes:

• An IDE tool: This is used for viewing and updating the code of the tests. The recommended IDE tool is Visual Studio Code, but other editors like IntelliJ Idea can also be used.

• Git: This is for version control of the code. It can be used directly in Visual Studio Code, in the command line, or with a tool like Sourcetree. The text also mentions some basic Git commands needed for test automation, such as clone, fetch, pull, stage, commit, push, create, merge branch.

• Node.js: This is required for using Cypress. While Cypress can be downloaded as an installation file without Node.js, having Node.js installed ensures clear functionality. The text also provides a command to check the installed version of Node.js.

• Npm (Node Package Manager): it is installed directly with Node.js and is commonly used for managing packages and dependencies in Node.js projects.

These tools are essential for setting up the environment and managing the codebase when using Cypress for test automation.

You need to have the following tools installed in order to use Cypress:

Using An IDE tool

Pricefx recommends the use of the Visual Studio is an integrated development environment (IDE) created by Microsoft. It is used to develop computer programs, websites, web applications, and mobile apps. Visual Studio supports multiple programming languages, including C#, C++, Visual Basic, F#, and others.

Visual Studio offers an extensive array of features designed to assist developers in coding, debugging, and testing their software. These capabilities encompass code editing, debugging, profiling, automated and manual testing, and seamless integration with various version control systems.

Moreover, Visual Studio supports extensions that enhance the functionality of the integrated development environment (IDE). Additionally, it provides tools for building and deploying applications across different platforms, including Windows, iOS, Android, and the web. In summary, Visual Studio serves as a comprehensive development environment that caters to the requirements of both individual developers and large development teams.

Using Git

Git is a version control system that is widely used in software testing to manage test code, test data, and test configurations. Here's how Git is used for software testing:

• Version Control: Git allows testers to version control their test code, test scripts, and test data. This ensures that changes to the test assets are tracked, and different versions of tests can be maintained.

• Collaboration: Testers can collaborate with developers and other team members by using Git to share and review test code and changes. This helps in maintaining transparency and coordination within the testing team.

• Branching and Merging: Git enables testers to create branches for new features or changes, allowing them to work on new tests without affecting the main test code. Testers can then merge their changes back into the main test codebase once the tests are ready.

• Continuous Integration: Git integrates with continuous integration (CI) tools, allowing testers to trigger automated tests whenever new code is committed. This ensures that tests are run regularly and that any issues are identified early in the development process.

• Test Automation: Test automation frameworks and test scripts can be stored in Git repositories, allowing testers to manage, update, and share automated tests effectively.

• Issue Tracking: Git repositories can be linked with issue tracking systems, enabling testers to associate test code with specific issues or requirements. This helps in tracking the status of tests and their relevance to the overall development process.

• Code Reviews: Testers can use Git to conduct code reviews for test scripts, ensuring that the quality of the test code meets the required standards.

By using Git for software testing, testers can ensure that their test assets are well-managed, changes are tracked, and collaboration with other team members is streamlined, ultimately contributing to the overall quality of the software being tested.

For version control of the code, Git can be utilized directly within Visual Studio Code, via the command line, or through a tool such as Sourcetree. Essential Git basics for developers include knowledge of commands such as clone, fetch, pull, stage, commit, push, as well as the ability to create and merge branches.

In the following screenshot, we highlight the Git version control system interface, specifically a GUI client that helps manage repositories. From this screenshot, we illustrate the following:

• Showing various branches within a repository, including feature branches, bugfix branches, and the develop branch. The branches are labeled with a naming convention that includes an issue or case identifier, such as "CASECORE-2805" or "C4SECORE-2415."

• Highlights where developers are working on different features and fixes, which are tracked by their respective branches.

• Displays a section for "Uncommitted changes," "Pending files, sorted by file name," "Staged files," and "Unstaged files," suggesting that there are changes that have been made locally but have not yet been committed to the repository.

• Shows that the uncommitted changes include merges from feature branches into the develop branch, which indicates that features or fixes have been completed and are being integrated into the main development line.

• The unstaged files listed at the bottom are JSON files located in a directory named "cypress/fixtures," which implies that these could be test data files used for automated testing with the Cypress testing framework.

In summary, the screenshot provides insight into the workflow of a software development team using Git for version control and possibly automated testing as part of their development process. The GUI client helps visualize the progress and organization of work within the repository.

c) Node.js

Link: https://nodejs.org/en/

• when you download cypress only as a installation file, it will work without node.js, but for clear functionality you need to have node.js installed

• You can check your actual version of node.js by command “node -v” in the command line

  

d) Package manager

• it is for installing and running plugins and dependencies for cypress tests (and cypress as well)

• on your computer needs to be installed one of the package managers (Npm or Yarn)

• npm is installed directly with Node.js

• locally you can choose, but on the server side it is used Yarn

Link: yarn install: https://classic.yarnpkg.com/en/docs/install/

• install Yarn in your command line: npm install --global yarn

  

Info:

• https://www.sitepoint.com/yarn-vs-npm/

• https://www.geeksforgeeks.org/difference-between-npm-and-yarn/