# About SimplifyQA Welcome to SimplifyQA, your comprehensive solution designed to streamline the entire software development lifecycle, making it accessible and efficient for everyone, regardless of coding skills or technical expertise. At SimplifyQA, our goal is to simplify your testing needs and save you valuable time and resources. SimplifyQA excels in managing both agile and non-agile teams, making it the ideal tool for diverse project environments. Whether you are working with Scrum teams, utilising Kanban boards, or employing other agile frameworks, SimplifyQA provides the flexibility and functionality to support your workflows. Agile teams can benefit from features like sprint planning, backlog management, and real-time collaboration, ensuring that everyone stays on the same page and project milestones are met efficiently. For non-agile teams, SimplifyQA offers robust project management tools that facilitate detailed work planning, resource allocation, and progress tracking. The intuitive interface allows for easy task management, timeline visualisation, and risk assessment, making it simple to oversee complex projects from start to finish. In addition to test automation, features like customisable dashboards, reporting, and analytics provide valuable insights into project performance, helping teams make informed decisions and continuously improve their processes. The landscape of modern software development has evolved from the days of punched cards and plugboards to the advanced use of microservices, CI/CD, and other cutting-edge technologies. Testing these sophisticated systems before deployment can be both challenging and time-consuming. However, with SimplifyQA, you can manage your entire project and scrum teams automate the testing process at every stage, ensuring faster, better, and safer software delivery while conserving time and resources. # Get Started with SimplifyQA SimplifyQA is an all-in-one **Application Lifecycle Management (ALM) and Test Automation** platform designed to streamline software testing and software development processes. It provides a user-friendly interface and powerful integrations to help teams collaborate, plan, develop, test, and deploy applications efficiently. ### Key Benefits of SimplifyQA * End-to-End Test Automation: Automate testing without extensive coding knowledge. * Seamless ALM Integration: Manage the complete application lifecycle in one place. * Collaborative Workflow: Enhance team productivity with role-based access and task management. * AI-Driven Insights: Gain intelligent recommendations to improve test coverage and efficiency. ### Who can use SimplifyQA? SimplifyQA is ideal for: * Developers – To track development progress and ensure seamless code integration. * Testers – To automate test cases and ensure software reliability. * Project Managers – To monitor project status, track bugs, and manage releases efficiently. ### How to Get Started? 1. Sign Up/Login – Create an account or log in to the SimplifyQA platform. 2. Set Up Your Project – Define your application, add team members, and configure testing environments. 3. Explore Key Features – Navigate through test case management, defect tracking, automation, and reporting dashboards. 4. Run and Analyze Tests – Execute manual or automated tests and generate insightful reports. # Agile & Non-Agile Framework SimplifyQA, a versatile Application Lifecycle Management (ALM) tool designed to streamline and enhance your project management processes. Whether you're working in an **agile** or **non-agile** environment, our product is equipped to adapt to your needs, ensuring seamless project execution and collaboration. You can configure the entire workflow of the projects as per your practice. In this section we will be discussing about the key features of various frameworks and learn how to configure the framework according to your needs. ## Key Features The key features of Agile and Non-Agile Framework are: ### Agile Framework An agile environment is a workplace or project setting that uses agile approaches for project management and software development. Agile cultures value flexibility, cooperation, and iterative development in order to adapt rapidly to changes and deliver high-quality products. 1. Sprint Planning and Management 2. User Story and Backlog Management 3. Kanban Boards 4. Scrum Meetings and Reports #### How to configure Agile Framework? Agile framework would be the default framework of SimplifyQA. The framework would be as shown below

Agile Framework in SimplifyQA

### Non-Agile Framework A non-agile environment, often known as a traditional or waterfall environment, takes a linear and sequential approach to project management and software development. This method is distinguished by extensive prior planning and a structured progression through distinct phases. 1. Waterfall Project Planning 2. Task and Resource Management 3. Gantt Charts 4. Documentation and Approval Workflows #### How to configure Non-Agile Framework? Non-Agile framework can be configured based on the structure or approach of certain projects and software development. Based on the workflow of your projects configure the environment accordingly. If you want to modify the framework and configure it according to your need, Layout can be modified in [Configure Page Layout](/admin-controls-and-configurations/manage-projects-and-users/configure-page-layout) for a particular project. # OS Support SimplifyQA supports all major operating systems, including **macOS**, **Linux**, and **Windows**. This cross-platform compatibility ensures that no matter what environment your team works in, SimplifyQA can seamlessly integrate into your workflow. By offering a consistent experience across different platforms, SimplifyQA helps teams collaborate more effectively, reduces friction, and ensures that everyone has access to the same powerful features. For automation, [download and install](/simplifyqa-installation-and-setup) the appropriate Wizard for Windows, macOS, and Linux. # SimplifyQA Hosting SimplifyQA is designed to provide maximum flexibility and scalability, catering to diverse project requirements and organisational needs. One of the key features of SimplifyQA is its deployment versatility: you can choose to host SimplifyQA either in the cloud or on-premises, depending on your specific needs and preferences. ### Hosting Options #### Cloud Hosting SimplifyQA can be hosted in the cloud, providing numerous benefits including scalability, accessibility, and reduced infrastructure management. With cloud hosting, you can access SimplifyQA from anywhere with an internet connection, ensuring seamless collaboration and real-time updates. **Getting Started with Cloud Hosting** 1. **Subscription and Setup** * Visit the SimplifyQA website and choose a cloud hosting subscription plan that suits your needs. 2. **Accessing SimplifyQA** * Once your cloud environment is set up, you will receive login details on your email. * Follow the instructions on mail and access SimplifyQA through the provided web portal using your credentials. 3. **Initial Configuration** * Configure your project settings, user roles, and permissions. * Set up your testing environment and start using SimplifyQA for your projects. #### On-Premises Hosting For organizations that require complete control over their data and infrastructure, SimplifyQA can be hosted on-premises. This option allows you to deploy SimplifyQA within your own data center, ensuring compliance with internal policies and regulatory requirements. **Getting Started with On-Premises Hosting** 1. **Subscription and Setup** * Visit the SimplifyQA website and choose the on-premises installation package. * Reach out to [support@simplify3x.com ](https://docs.simplifyqa.ai/)or [infra@simplify3x.com](mailto:undefined) to initiate the subscription process and share your requirements. 2. **System Requirements** * Ensure your servers meet the minimum system requirements specified in the [installation guide.](/get-started-with-simplifyqa/simplifyqa-hosting/on-premise-installation-guide/pre-requisites) * Set up necessary dependencies and prerequisites before installation. 3. **Configuration and Setup** * Configure network settings, database connections, and user authentication as specified in the [installation guide.](/get-started-with-simplifyqa/simplifyqa-hosting/on-premise-installation-guide/installation-guide) * Set up your testing environment, user roles, and permissions. 4. **Maintenance and Updates** * Regularly check for updates and patches from SimplifyQA. Release notes would be shared to keep you posted on the new updated and patches. * Apply updates manually to ensure your system remains up-to-date and secure. # On-premise Installation Guide ### Getting Started This is an overview of requisites and detailed on-premise deployment procedures for SimplifyQA. 1. [Pre-requisites](/get-started-with-simplifyqa/simplifyqa-hosting/on-premise-installation-guide/pre-requisites) 2. [Installation Guide](/get-started-with-simplifyqa/simplifyqa-hosting/on-premise-installation-guide/installation-guide) # Pre-requisites ### System Requirements 1. **Database Server**
Hardware RequirementSoftware Requirement
Ubuntu v16.*Docker v18.*
8 coresudo access (root user)
32 GB RAM
500 GB Disk space
2. **Application Server**
Hardware RequirementSoftware Requirement
Ubuntu v16.*Docker v18.*
8 coresudo access
32 GB RAM
500 GB Disk space
3. **Cloud Server** Cloud server would be required only if you subscribe for cloud execution in SimplifyQA.
Hardware RequirementSoftware Requirement
Ubuntu v16.*Docker v18.*
8 coresudo access
32 GB RAM
500 GB Disk space
> For more details to subscribe for cloud executions contact **** or visit our website. * Download the below listed dockers files from the secured link provided in email and copy to Application and Database Server 1. simplifyqaweb.tar 2. simplifyqarabbitmq.tar * Remote access to you Server VPN (Access to VPN if present). * Secured shell access. Login credentials of SSH (if present). # Installation Guide #### Database Server Setup * Install docker version 18.\* from repository. ``` sudo apt-get update ``` ``` sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ Software-properties-common ```
``` curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - ```
``` sudo apt-key fingerprint 0EBFCD88 ``` ``` sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" ```
* Check if the docker is installed in the machine by running the following command ``` sudo docker -v ``` * Other images needed from docker hub is : **Mongo 4.0.0** ``` docker pull mongo:4.0.0 ```
* Load and run Mongo Docker image by navigating to the download directory ``` docker run -d --name simplifyDB -p 27017:27017 -v ~/simplifyqa_db:/data/db -e MONGO_INITDB_ROOT_USERNAME= -e MONGO_INITDB_ROOT_PASSWORD= mongo:4.0.0 ```
* Run the following command to create User in mongoDB ``` docker exec -it simplifyDB mongo -u -p --authenticationDatabase admin --eval "db.createUser({user: '', pwd: '', roles:[{role:'readWrite', db: 'bolt'},{role:'dbAdmin', db: 'bolt'}]});" bolt ``` > Boltupload and mongodata will be provided in email. Unzip the Provided files. * Verify if the docker is up and running by executing the following command ``` sudo docker ps -a ```
#### Application Server Setup * Install docker v18.\* from repository and check docker version ``` sudo docker -v ``` * Other images needed from docker hub are: RabbitMQ:3-Management and Node:12 ``` 1. docker pull rabbitmq:3-management 2. docker pull node:12 ``` * Download the docker image simplifyqa.tar and rabbitmq.tar file from the secure lnk using the following command ``` docker load -i .tar ```
> Note: tar files would be provided over email. #### Backup Server Setup The db dump path from the file system will be configured for backup purposes. **App Server Configuration** * Execute the following command to run our Application ``` docker run -d -p 4011:4011 -v /root/boltupload:/root/boltupload -v /root/simplifyQA/projectconfig.js:/simplifyqaweb/config/projectconfig.js -v /root/simplifyQA/logs/qaserver.log:/var/log/simplifyqa.log -v /etc/hosts:/etc/hosts simplifyqaweb ```
* Run the following command to check running containers ``` docker ps ``` * Update projectconfig.js in application server with below content ``` 1."dburl": "mongodb://:@dbserverIP:27017/bolt" 2."dblogUrl": "mongodb://:@dbserverIP:27017/bolt" 3."serverUrl": "http://serverIP:4011" 4."executionIp": "serverIP:4011", 5."rabbitUrl":"amqp://:@serverIP:5671" ``` **Email Configuration** * Update SMTP E-mail configuration in both projectconfig.js file in application project as well as simplifyRabbitMQ . ``` "email": "no-reply@companyname.com", "mail_perpose_forgot": "Generating forgot password", "mail_perpose_new": "Generating new password", "mail_subject_new": "Welcome to company name", "mail_subject_forgot": "New password to login", "smtp_host": "SMTP hostname", "smtp_port": SMTP Port, "secure":true/false, "mail_from":"from-email", "simplify3x_username": "email",//for smtp authentication "simplify3x_password": "password" ```
**MQ Configuration** * Eecute the below command to run RabbitMQ:3-Management Docker Image ``` docker run -d --hostname rabbitmq --name qarabbitmq -e RABBITMQ_DEFAULT_USER= -e RABBITMQ_DEFAULT_PASS= -p 5671:5672 -p 15671:15672 rabbitmq:3-management ```
* Execute the below command to for changes to be made in SimplifyQARabbitMQ projectonfig.js file before running the simplifyRabbitMQ Docker image ``` 1."dburl": "mongodb://:@dbserverIP:27017/bolt" 2."rabbitUrl":"amqp://:@serverIP:5671" 3. “serverUrl": "http://serverIP:4011” ``` * Execute the simplifyRabbitMQ Docker Image ``` docker run -d -v /root/simplify-RabbitMQ/projectconfig.js:/simplifyqarabbitmq/configuration/projectc onfig.js -v /root/simplify-RabbitMQ/logs/simplifyqarabbitmq.log:/var/log/simplifyqarabbitmq.log simplifyqarabbitmq ```
* Create file simplifyqarabbitmq.log within logs directory ``` mkdir logs ``` > **Note:** In this Example have mounted projectconfig.js file outside the project folder of both simplifyQA application and SimplifyQA rabbitMQ. ssh username\@Ipaddress ubuntu 18.04 machine #### Troubleshooting on-premise deployment * Execute the below command to view the SimplifyQA app logs ``` File Location: projectfolder/logs/qaserver.logs ```
* Execute the below command to view the SimplifyQA RabbitMQ logs ``` File Location: projectfolder/logs/simplifyqarabbitmq.log ```
# Support and Resources * **Online Documentation**: Access detailed guides and tutorials on the SimplifyQA website. * **Customer Support**: Contact our support team at for assistance with any issues or questions. * **Community Forums**: Join the SimplifyQA community to share experiences and solutions with other users. # Training and Onboarding * **Webinars and Workshops**: Participate in training sessions to learn about SimplifyQA features and best practices. * **Onboarding Assistance**: Get personalised onboarding support to help you set up and configure SimplifyQA for your organization. # Explore SimplifyQA for your Application Lifecycle Management SimplifyQA is a powerful **Application Lifecycle Management (ALM) platform** designed to help organizations manage the entire **software development and testing process**. It provides an **integrated, structured, and automated approach** to software lifecycle management—from **project initiation to deployment and maintenance**. With **SimplifyQA**, teams can collaborate efficiently, automate testing, and accelerate software releases while ensuring high quality. Below is an in-depth look at how to use SimplifyQA for **ALM**. ### Getting Started with ALM in SimplifyQA **Create a Project** To begin managing your application lifecycle, you need to set up a new project in SimplifyQA: * Define the project name, description, and scope. * Assign team members and roles (Developers, Testers, Managers). * Configure project settings, including test environments and integrations. ### Requirement Management **Add Requirements** * Capture business and functional requirements for the application. * Link requirements with test cases and user stories to maintain traceability. * Define priorities and dependencies to align teams on project goals. ### Agile & Backlog Planning **Plan Backlog** * Create and prioritize a product backlog with user stories. * Organize work into epics, features, and user stories. * Use the Kanban board to visualize work progress. **Add Tasks** * Break down backlog items into actionable tasks. * Assign tasks to team members with due dates and priorities. * Monitor task status in real-time to track progress. **Sprint Tracking** * Plan and run Agile sprints using SimplifyQA’s sprint management module. * Track sprint velocity, team productivity, and completed tasks. * Adjust sprint scope based on progress and blockers. ### Test Management & Automation **Write Scenarios** * Create test scenarios based on functional requirements. * Organise them into modules for better test coverage. **Automate Scenarios** * Convert manual scenarios into automated test cases. * Use SimplifyQA’s codeless automation. **Add Reusable Functions** * Build reusable test functions to streamline automation. * Reduce redundancy and improve maintainability of test scripts. **Debug Tests** * Run test cases in debug mode to identify failures * View logs and error traces to resolve issues. **Add to Suite** * Group test cases into test suites for structured execution. * Define execution sequences and dependencies. **Data-Driven Testing** * Use parameterised testing by linking test cases to datasets. * Ensure coverage for multiple data scenarios with minimal effort. ### Test Execution & Reporting **Run & Analyse your Suite** * Execute test suites manually or schedule them for automated runs. * Monitor test execution status in real time **View Reports** * Generate detailed test execution reports with insights into pass/fail rates. * Analyse test trends, defect density, and requirement coverage. **Schedule Test Runs** * Automate test execution by scheduling test runs at specific intervals. * Reduce manual intervention and ensure continuous quality validation. **Pipeline Integration** * Integrate SimplifyQA with CI/CD pipelines (Jenkins, Azure DevOps). * Automate build verification testing as part of deployment workflows. ### Defect Management **Log Defects** * Capture defects with detailed logs, screenshots, and system info. * Assign defects to developers with priority levels. * Track defect resolution and retest fixes efficiently. ### Why Choose SimplifyQA? * Complete Lifecycle Management – From planning to deployment in one platform. * Seamless Automation – Codeless automation to reduce effort and enhance efficiency. * Agile & DevOps Ready – Sprint management, backlog tracking, and CI/CD integration. * Scalability & Security – Enterprise-ready with role-based access and secure collaboration. With SimplifyQA, teams can accelerate software development, reduce defects, and deliver high-quality applications faster. *** ### Frequently Asked Questions (FAQs)
What is SimplifyQA used for? SimplifyQA is an Application Lifecycle Management (ALM) and Test Automation platform that helps teams manage projects, automate testing, track defects, and ensure software quality throughout the development lifecycle.
Do I need coding skills to automate tests in SimplifyQA? No! SimplifyQA is a No Code/Low Code platform which provides codeless test automation, allowing testers to create automated test cases without programming knowledge. However, advanced users can integrate scripting when needed.
How does SimplifyQA support Agile development? SimplifyQA includes backlog management, sprint planning, task tracking, and Agile dashboards, making it easy for teams to manage Agile workflows effectively.
Does SimplifyQA support data-driven testing? Yes, SimplifyQA allows parameterized testing, letting you run the same test with multiple data sets to improve test coverage.
Is SimplifyQA suitable for large enterprise teams? Absolutely! SimplifyQA is scalable and secure, supporting enterprise-level teams with role-based access, cloud and on-premise deployment options, and collaboration features.
# SimplifyQA Installation & Setup Setting up **SimplifyQA** is the first step toward achieving streamlined test management and automation. Whether you are using the cloud version or an on-premise installation, the setup process is designed to be quick and efficient. SimplifyQA supports seamless integration with CI/CD pipelines, defect tracking tools, and version control systems, ensuring a well-connected testing ecosystem. With a user-friendly interface, teams can easily configure projects, define roles, and set up automated test execution. Proper setup ensures that teams can manage the entire **Application Lifecycle Management (ALM)** process with ease, from planning and execution to reporting and defect tracking. ### Setting up the SimplifyQA Agent - QAWizard The **QAWizard** is an essential component for executing automated test cases, enabling local and remote test execution across different environments. It acts as a bridge between the SimplifyQA platform and the underlying test infrastructure, ensuring smooth communication and execution. After installation, the SimplifyQA Agent runs in the background, enabling **scheduled test execution, parallel runs, and real-time status updates**. It ensures that test scripts execute consistently across different environments, whether on **local machines, or cloud servers**. By setting up the agent correctly, teams can automate test execution at scale, enhance test reliability, and ensure faster release cycles. # Setup QAWizard Wizard is the SimplifyQA Agent which is required to use any automation features in SimplifyQA. In this section, we’ll guide you through how to setup and install Wizard and start automating. ## Download the Wizard * Navigate to Downloads: Locate your profile once you login to SimplifyQA. Navigate to Settings -> Downloads * Download the Wizard: Choose the appropriate OS and download the latest version of Wizard. To view previous versions, refer to the help doc.
## Install the Wizard * Install Wizard: Run the Wizard by double clicking on the file which is downloaded, SimplifyQA.exe in Windows and SimplifyQA.dmg in MAC. * Provide the Token: Navigate to SimplifyQA and go to Profile -> Manage Accounts -> Security. Copy the token for Machine Registration and provide this token in the Wizard which is prompting for token.
* Install Packages: Choose the package you want to use and click on ‘Install Packages’. Note that the list of packages are displayed based on the licenses subscribed. * Verification: Navigate to SimplifyQA and verify for the agent icon to be turned green.
## Frequently Asked Questions (FAQs)
Wizard is not getting installed in my system, Why? Ensure that your machine has right permissions to install any external software’s. If the organization policies are blocking external software’s from installing, you may have to contact your administrator to get SimplifyQA Wizard whitelisted.
Why doesn’t the agent icon in SimplifyQA turn green? a. Ensure SimplifyQA Wizard is running in your machine. If not turn on the Wizard from either browser or from the location of the Wizard. b. Verify the SimplifyQA logs to ensure that there were no errors while installing the packages. If any errors were encountered, try un-installing the agent and install again. c. Ensure to provide the correct during the installation. If the token is incorrect or expired, wizard wouldn't start and turn green in SimplifyQA.
Why am I not able to install the packages? a. Check if the agent is already running. If it is already running go to Wizard icon in system tray and select ‘Stop’ option (do not select ‘Exit’ option). Now navigate to Package manager and retry ‘Install Packages’ b. Make sure you have uninstalled the previous version before installing the new version. c. If none of the above is working, try re-installing the wizard else reach out to SimplifyQA support team.
Why can't I find the Android package option in the Wizard? You might not have the necessary licenses for Android automation, which is why the Android package option isn't visible. Please reach out to SimplifyQA sales to obtain the licenses. If you have acquired the licenses but still don’t see the option, please contact the support team.
# Register QAWizard This document provides instructions on registering QAWizard for both local and remote machines. Registration occurs automatically when you install the agent. * **Installation**: When you install the QAWizard on your local or remote machine, the registration process will automatically take place. * **Verification**: You can verify the registration status by navigating to the **Machine Registration** section in SimplifyQA. ### Checking Registered Machines 1. Login to SimplifyQA application. 2. Navigate to the **Profile -> Settings -> Configuration -> Machine Registration** section. 3. Here, you will find a list of all registered machines, both local and remote. 4. Identify your machine with the IP address if your machine is registered.
{% hint style="info" %} **Troubleshooting** * If you do not see your machine listed after installation, ensure that the agent has been installed correctly. Try uninstalling the agent and re-installing it. * For further assistance, contact the support team. {% endhint %} # Register your Machine To execute tests using SimplifyQA, you must first register your machine. This ensures the platform can communicate with your execution environment effectively. {% hint style="success" %} **Note:** When the agent is first installed and started, SimplifyQA automatically registers the machine by default. This registration feature can be used to manually register virtual or remote machines. {% endhint %} ### Steps to Register your Machine * Log in to SimplifyQA and click on your profile icon in the top right corner. * From the dropdown menu, select **Settings**, then go to the **Configuration** section.

Profile Menu Navigation

* Click on the **Registration** tab, and then move to the **Machine Registration** sub-tab. * Click the '**+ Machine'** button to begin the registration process.

Machine Registration Tab

* Choose Machine Type: * **Local Machine:** If you're registering a local machine, details such as **Machine Name**, **IP Address**, and **Machine Address** will be automatically populated. * **Remote Machine:** If it's a remote machine, you'll need to manually input: Machine Name, IP Address, and Machine Address

Local Machine

Remote Machine

* Once all necessary fields are completed, click on **Register**. Your machine will now be registered with SimplifyQA.

Registered Machine

* Color Indicators for Machine Status: * **Green**: The machine is registered and the agent is running successfully. * **Red**: The machine is either not registered or not active. * **Grey**: The machine is registered, but the agent is not currently running. * You can delete any registered machine by clicking the delete icon next to it. * To rename a machine, simply click on the machine’s name input field and make the necessary changes. After successful registration, the machine becomes available for use in your test executions. Make sure the SimplifyQA agent is running on the registered machine to enable smooth communication and execution. # Setup Android Device Configuring an Android device for testing is essential for executing mobile test cases seamlessly. Teams can perform both manual and automated testing, ensuring robust functionality and performance across multiple Android platforms. With a configured Android device, teams can perform functional, regression, and UI testing efficiently. Test execution can be triggered locally or remotely, ensuring scalability across multiple environments. Additionally, integrating the device with CI/CD pipelines enables continuous testing, providing real-time feedback on application performance and stability. # How to enable settings in android device? To effectively automate testing on Android devices, you'll need to configure your device and set up the necessary tools. In this section, we'll walk you through the essential steps to setup any android device required for automation in SimplifyQA. ### Samsung * Developer options * Go to Settings >About Phone
* Tap Software Info > Build Number
* Tap Build Number seven times. After the first few taps, you should see the steps counting down until you unlock the developer options. You may also have to tap in your PIN for verification.
* Next, navigate to Settings > Developer Options and turn on the Developer Options.
* Now, enable the following settings in the Developer Options section. * USB debugging * Install via USB * USB debugging (Security settings) * Wireless display certification * Enable Wi-Fi verbose logging * Wi-Fi scan throttling * Adaptive notification priority * Stay awake * Verify bytecode of debuggable apps
### Xiaomi Redmi * Developer options * Go to Settings >About Phone > MIUI version * Tap on “MIUI version” for 7 times until developer mode appears
* Next, navigate to Settings > Additional Settings > Developer Options and turn on the Developer Options option.
* Now, enable the following settings in the Developer Options section. * Stay awake * OEM unlocking * USB debugging * Install via USB * USB debugging(security settings) * Wireless display certification * Wi-Fi scan throttling * Tethering hardware acceleration * Verify bytecode of debuggable apps
### Oppo * Developer options * Go to Settings >About Phone * Tap on Software Info > Build Number. * Tap Build Number seven times.
* Next, navigate to Settings >Developer Options and turn on the Developer Options option. * Now, enable the following settings in the Developer Options section. * USB debugging * Verify bytecode of debuggable apps * Disable Permission monitoring * Show surface updates * Wi-Fi scan throttling * Mobile data always active * Enable absolute volume
### Huawei * Developer options * Go to Settings >About Phone * Tap on Software Info > Build Number * Tap Build Number seven times
* Next, navigate to Settings >Developer Options and turn on the Developer Options option. * Now, enable the following settings in the Developer Options section. * Stay awake * Enable OEM unlock * USB debugging * Always prompt when connecting to USB * Allow ADB debugging in charge only mode
### Vivo * Go to Settings>My Device * Click on More Parameters. Tap on Software version 7-10 times.
* Next, navigate to Settings > Developer Options and turn on the Developer Options option.
* Now, enable the following settings in the Developer Options section. * USB debugging * Disable Bluetooth A2DP hardware offload * OEM unlocking
### One Plus Developer options * Go to Settings >About Phone * Tap on Software Info > Build Number * Tap Build Number seven times
* Now, enable the following settings in the Developer Options section. * OEM Unlocking * USB Debugging * Navigate to Default USB configuration in developer options and choose File Transfer
# How to register android device? Device registration is a process that links your Android device to SimplifyQA to enable automation on those android devices. In this section, we'll guide you on how to register the android device. **Steps to Register Your Android Device** * Login to SimplifyQA application. * Ensure that all the settings as guided in previous section is enabled before registering * Navigate to the **Profile -> Settings -> Configuration -> Android Registration** section.
* Here, you will find a list of all registered and unregistered devices. * Identify the device which is connected to your machine and click 'Register' button to register your device. Rename the device name(if required) for better identification of the devices in future.
* Navigate to Wizard icon in SimplifyQA to ensure that the device is displayed in the dropdown.
Why is my android device not getting displayed in SimplifyQA? You android might not be getting displayed in SimplifyQA because of one of the below reasons: * Connectivity issue: Ensure the USB cable connecting your device to the machine is securely plugged in. A loose connection may prevent the device from being detected in SimplifyQA. Check the USB cable for any damage or wear. If the cable is faulty, it could interfere with the device's connection to SimplifyQA. * Device not registered: You may have connected the device, but it might not be registered in SimplifyQA. Please ensure that the Android device is properly [registered](/simplifyqa-installation-and-setup/setup-android-device) within the SimplifyQA platform. * Developer Settings: Ensure that the Android device is properly set up with the required settings for automation.. Check out '[Setup Android Device for Automation](broken://pages/8tRqxACMas7jcDuEjnv8)'.
# Setup emulators on Android Studio for automation in SimplifyQA Using Android emulators in Android Studio allows testers to execute automated test cases without needing a physical device. This setup ensures that applications are tested across different device configurations, screen sizes, and OS versions. Below are the steps to configure an emulator and integrate it with SimplifyQA for automation. ### Prerequisites Before setting up the emulator, ensure the following: * **Android Studio is installed** on your system. * **Android SDK and Virtual Device Manager** are configured. * **QAWizard is stopped** to prevent execution conflicts. ### Launching the Virtual Device in Android Studio 1. Open Android Studio and navigate to the home screen.
2. Click on the "**More Actions"** dropdown and select "**Virtual Device Manager"**.
3. By default, a virtual device will be available in the list. 4. Click on the **three-dot menu** next to the listed device and select "**Cold Boot"** (preferred) or directly click on the "**Run"** icon.
5. The emulator will launch and be ready for testing. ### Connecting the Emulator with SimplifyQA 1. Once the emulator is running, **open the SimplifyQA application**. 2. Click on the **Connect Devices** icon.
2. Switch to the **Virtual Device** tab.
3. The emulator name should now be listed under the available devices.
### Adding a New Emulator in Android Studio If you need to test on different devices, follow these steps: 1. Navigate to "**More Actions** → **Virtual Device Manager"**. 2. Click on the **"+"** icon to add a new emulator.
3. From the left panel, choose the **device type** (Phone or Tablet). \ Example: Select Phone for mobile testing. 4. Select the desired **device model** and click **Next**.
5. If required, **download additional system images or packages** (confirm the popup)
6. Once the download is complete, click **Finish**.
6. The new emulator will now be listed in the Device Manager and available for automation in SimplifyQA.
By setting up emulators correctly, teams can efficiently perform automated testing across multiple Android devices, ensuring application stability and compatibility. ### Frequently Asked Questions (FAQs)
My emulator is not showing up in SimplifyQA. What should I do? If the emulator is not listed under **Virtual Devices** in SimplifyQA: * Ensure that the emulator is running in Android Studio. * Restart the SimplifyQA application and click on Connect Devices again. * Make sure QAWizard is stopped before launching the emulator. * Check if the ADB (Android Debug Bridge) is enabled and running correctly.
Can I test different screen sizes and Android versions using emulators? Yes, you can add multiple emulators with different screen sizes and OS versions in Virtual Device Manager. This helps in testing application compatibility across different Android devices.
# Setup iOS Device Configuring an iOS device for testing allows teams to execute manual and automated test cases seamlessly across different Apple devices. Once the device is connected to the testing framework, it can be used to validate application functionality, UI responsiveness, across various iOS versions. **SimplifyQA’s automation framework** enable smooth integration, ensuring compatibility with different screen sizes and device types. With a properly configured iOS device, testers can execute test cases both locally and remotely. Integration with CI/CD pipelines ensures continuous testing, enabling faster feedback loops and improved application stability. By leveraging cloud-based or real-device testing environments, teams can scale their test coverage efficiently, ensuring a high-quality user experience across all iOS platforms. # How to setup and register iOS device? This guide provides step-by-step instructions to register an iOS device and set up the required certificates and provisioning profiles in the Apple Developer Account for mobile automation in SimplifyQA. ### Prerequisites **For Windows Users:** 1. Download and install the iTunes application. 2. Connect the iOS device to your Windows system.
3. Click on the Register button in the SimplifyQA tool. 4. A valid Apple Developer Account is required to automate iOS applications. 1. Enter the email address associated with your Apple Developer Account. 2. If you do not have an account, visit the [Apple Developer Portal](https://developer.apple.com/) to create one. 5. Click Next to proceed.
**For Mac Users:** 1. Connect the iOS device to your Mac. 2. Click on the Register button in the SimplifyQA tool.
3. A valid Apple Developer Account is required to automate iOS applications. 1. Enter the email address associated with your Apple Developer Account. 2. If you do not have an account, visit the [Apple Developer Portal](https://developer.apple.com/) to create one. 4. Click Next to continue.
*** **Generate a Certificate Signing Request (CSR)** 1. Click the Generate CSR button in SimplifyQA. 1. The CSR file will be downloaded automatically. 2. Click Next to proceed.
*** 3\. Create a Developer Certificate * Open the [Apple Developer Portal](https://developer.apple.com/) and log in to your Apple Developer Account.
* Go to Account > Certificates.
* Click on the "Certificates +" button to add a new certificate.
* Select Apple Development radio button and click Continue.
* Click Choose File, select the CSR file downloaded earlier, and upload it to the Certificates section in the Apple Developer Portal and Click Continue.
* Then click Download to download the iOS Development Certificate.
* Upload the iOS Development Certificate in SimplifyQA and click Next.
* Go back to the Apple Developer Portal, navigate to Devices, and click on the "+" icon to add a new device.
* Enter the Device Name and Device ID (UDID), then click Continue.
* Click Register to add the device.
* Click Done to complete the device registration.
*** **Create a Provisioning Profile** * In the Apple Developer Portal, navigate to Profiles and click on the "+" button.
* Select iOS App Development and click Continue.
* Under App ID, always select XC Wildcard (\*\*\*\*\*\*\*), then click Continue.
* Under Select Certificates, check Select All, then click Continue.
* Under Select Devices, check Select All, then click Continue.
* Enter a Provisioning Profile Name, then click Generate.
* Click Download to save the Provisioning Profile Certificate.
* Open SimplifyQA, upload the Provisioning Profile Certificate, and click Finish Adding Device.
*** **Activate the Provisioning Profile in SimplifyQA** * Click on the iOS Registration button on the pop up.
* Click the Activate button to activate the newly added Provisioning Profile Certificate.
* Once activated, the Activate button will change to Activated (displayed in green).
* Under iOS Registration, navigate to All Devices. * Click the Register button on the device card to complete the device registration process.
# Single Sign-On (SSO) You can use Single sign-on (SSO) to log into your SimplifyQA account via existing SAML-enabled ID providers. Here's how you configure SAML SSO for SimplifyQA using Azure Active Directory: ### Add SimplifyQA from the gallery To configure the integration of SimplifyQA into Azure AD, you need to add SimplifyQA from the gallery to your list of managed SaaS apps. 1. Sign in to the Azure portal. 2. On the left navigation pane, select the ‘Azure Active Directory’ service. 3. Navigate to ‘Enterprise Applications’ and then select ‘All Applications’. 4. To add a new application, select ‘New application.’ 5. Click on "Create your own Application". Give a name to your application and create it. ### Configure and test Azure AD SSO for SimplifyQA 1. Login to your SimplifyQA account. 2. Simultaneously, log in to your Azure portal, navigate to the SimplifyQA application integration page, find the Manage section in the sidebar, and select single sign-on. 3. \[Azure Portal] On the Select a single sign-on method page, select SAML. 4. \[Azure Portal] On the Set up single sign-on with SAML page, click the edit/pen icon for Basic SAML Configuration to edit the settings. 5. Under Security, you can enable SSO and choose Azure AD using SAML as the SSO you want to set up. From S’implifyQA Dashboard, you will be presented with the ACS URL and Entity ID. Copy the values and enter the values in the relevant fields in the Azure AD portal. To be more specific: * In the ‘Identifier (Entity ID)’ field, enter the SP Entity ID from the SimplifyQA security settings page. * In the ‘Reply URL’ field, enter the Assertion Consumer Service(ACS) URL from the SimplifyQA security settings page. * In the ‘Sign-on URL’ field, enter your login URL 6. \[Azure Portal] On the Set up single sign-on with SAML page, click the edit/pen icon for User Attribute & Claims to edit the settings. 7. \[Azure Portal] Select the Unique User identifier as user.mail. The name-id format should be unspecified. 8. \[Azure Portal] Click Save on the top left once done. 9. \[Azure Portal] Once you configure SimplifyQA as an SP, you will be given values for the following entries in the Azure AD Portal. * Entity ID (or Metadata ID) * SAML SSO URL (or Login URL) * Security Certificate (or x.509 certificate) Note: On the set-up single sign-on with SAML page, in the SAML Signing Certificate section, find Certificate (Base64) and select Download to download the certificate and save it on your computer. 10. Copy and paste in relevant fields in the SimplifyQA dashboard. To be more specific: * In the ‘Entity ID Provided by the IdP’ field, copy the Azure AD Identifier URL. * In the ‘SAML SSO URL’ field, copy the Login URL from the Azure portal. * Under ‘Signing Options’, choose ‘Only Signed Assertions’ (By default, this would be chosen. If you have modified the signing in Azure app, select accordingly) * Open the Base64 encoded certificate in notepad, copy its content and paste it into the Security certificate text box. 11. Click on save.
# Get to know your Workspace The SimplifyQA workspace is designed to provide a structured and user-friendly environment where teams can manage the entire testing lifecycle, from requirement management to test execution and defect tracking. This guide will walk you through the key modules of the SimplifyQA workspace, helping you understand how to navigate, manage, and optimize your testing workflows. 1. **My Board** The My Board module serves as a personalized dashboard where users can track their assigned tasks, defects, and pending work. It provides: * A quick overview of assigned user stories, defects, and tasks. * Status tracking for ongoing tasks. 2. **Release Management** The Release Management module helps teams plan and track different versions of their application. It enables: * Creating and managing releases for structured software delivery. * Mapping test cases and defects to specific releases. * Tracking progress to ensure all required tests and bug fixes are completed before deployment. 3. **Requirement Management** The Requirement Management module allows teams to define, document, and track requirements efficiently. Key features include: * Creating and managing user stories and functional requirements. * Linking test cases to requirements to ensure full coverage. * Tracking requirement changes and version history for traceability. 4. **Test Management** The Test Management module is the core area for handling test cases and test plans. It provides: * A structured repository for test cases, scenarios, and suites. * Version control for tracking changes in test cases. * Test categorisation based on modules, features, or functionalities. * Ability to link test cases to requirements and defects. 5. **Test Execution** The Test Execution module provides options to execute test cases manually or automate them for faster validation. Key functionalities include: * **Manual & Automated Execution:** Run test cases manually or integrate them into an automation framework. * **Data-Driven Execution:** Execute the same test case with multiple data sets. * **Parallel Execution:** Run tests across multiple devices, browsers, and environments simultaneously. * **Scheduled Execution:** Set up automated test runs at predefined times. * **Real-Time Monitoring:** View execution logs, track failures, and analyse test results instantly. 6. **Defect Management** The Defect Management module is essential for tracking and managing bugs effectively. It includes: * Logging new defects and assigning them to developers for resolution. * Linking defects to test cases for better traceability. * Tracking defect status (Open, In Progress, Resolved, Closed). * Integration with defect tracking tools like JIRA. * Generating defect reports for trend analysis and issue prioritisation. 7. **Marketplace** The Marketplace module allows users to explore and integrate third-party tools, plugins, and add-ons that enhance testing workflows. It includes: * Integrations with CI/CD tools (Jenkins, Azure DevOps). * Defect tracking integrations (JIRA). * Automation framework extensions (Selenium, Appium). * Custom utility plugins for advanced reporting and analytics. 8. **User Profile & Admin Controls** Users can access their profile settings and switch to admin mode for advanced configurations. * **User Profile Management:** Update personal details, preferences, and notification settings. * **Switch to Admin Mode:** Access admin controls for managing users, projects, roles, and security settings. * **Role-Based Access Control:** Manage user permissions and restrict access based on roles. ### Frequently Asked Questions (FAQs)
How do I switch between different projects? Click on the Project Dropdown in the top menu and select the desired project.
Can I customise my dashboard to focus on specific metrics? Yes, the users can customise the dashboards according to the requirements and needs.
How do I add a new integration from the Marketplace? Navigate to the Marketplace, select the desired integration, and follow the setup instructions.
Who can access admin controls in SimplifyQA? Only users with Admin Privileges can manage system settings, user roles, and security configurations.
Can I schedule test executions in advance? Yes, SimplifyQA allows users to schedule test runs at specific times using the Scheduled Execution feature.
# Blueprint of SimplifyQA In this section, gain insights into the overall layout and design of the workspace, including how to access various sections and navigate through the system.
# Key Terminologies In this section, we'll be providing detailed descriptions of each module within the SimplifyQA, highlighting their functions and how they interconnect to support your workflow. **What is Admin?** An admin, short for administrator, is a super user with extensive authority. Admins can create projects, manage users, configure roles and privileges, set up teams, customize layouts and fields, manage clients, view and alter sessions, change password policies, and adjust integration settings, among other tasks. **What is Non-Admin/User?** A non-admin/user is any person's account created by an admin with privileges set by the admin. Non-admin users play a crucial role in the tool, interacting with various modules such as Planning, Requirement Management, Test Management and Execution, and Defect Management. These users can be anyone involved in software development and management, including developers, testers, project managers, and other stakeholders in the process. **What is a Team?** **Teams** are cross-functional groups of individuals who work together collaboratively to deliver incremental and iterative improvements to a product or project. Agile teams are designed to be self-organising and empowered to make decisions, with a focus on delivering value to customers through continuous delivery of high-quality software. **What is Password Policy?** A **password policy** is a set of rules defined by an admin that users must adhere to when setting or updating their passwords. **What is a Project?** In SimplifyQA, all modules of the tool are organised around a project. Each module, including suites, user stories, test cases, functions, objects, parameters, defects, and tasks, is mapped under a project. **What is Session?** **Sessions** refer to the interval that users have been logged in to SimplifyQA. Admins also have the option to force logout any user during from session module. **What is force logout?** An **action** available for admins to terminate a user’s session in the tool. **What is a Wizard (formerly known as Agent)?** **Wizard** is a software package which needs to be installed in the machine to create and execute automation tests. **What is an Epic?** An **Epic** is a substantial body of work that can be broken down into smaller tasks or stories. It represents a significant piece of functionality or a major feature within a software project. EPICs provide a high-level overview of what needs to be achieved and help in organizing and prioritizing the development process. They are often used in agile project management to encapsulate larger goals that will be accomplished through multiple iterations or sprints. **What is a Feature?** A **feature** is a specific piece of functionality or capability within a software application that provides value to the user. Features are smaller and more focused than EPICs and are often components or aspects of larger goals. They represent distinct aspects of the system that users can interact with or experience, such as a search function, a reporting tool, or a user authentication system. Features are typically defined and developed to enhance the usability, performance, and overall value of the software. **What is a User Story?** A **user story** is a short, simple description of a software feature or functionality from the perspective of the end user or customer. It captures what the user wants to achieve and why, providing a clear and concise requirement that helps guide development. User stories are a key element of agile methodologies, focusing on delivering small, incremental improvements that add value to the user. **What is a Release Plan?** A **release plan** is a detailed roadmap that outlines the schedule, scope, and timeline for delivering a set of features or functionalities in a software project. It helps coordinate and communicate the planned releases to all stakeholders, ensuring that everyone is aligned with the project's goals and timelines. **What is Requirement Traceability Matrix (RTM)?** A **Requirement Traceability Matrix (RTM)** is a document that maps and traces user requirements with test cases. It ensures that all requirements defined for a system are tested in the test protocols. The main purpose of RTM is to ensure that all requirements are covered by test cases, and it provides a means to track the status of project requirements and test coverage. **What is Module and Sub-module?** A **module** is a higher-level grouping of related artefacts that together form a significant part of the software's functionality. A **sub-module** is a lower-level grouping within a module, which further organises artefacts into more specific categories or functionalities. **What is a Task?** A **task** is a specific piece of work or activity that needs to be completed within a project. It is a basic unit of work, often detailed enough to be assigned to an individual or a team and tracked through to completion. Tasks are used to break down larger work items, such as user stories, features, or projects, into manageable parts. They help in planning, tracking progress, and ensuring that work is carried out efficiently and effectively. **What is a Defect?** A **defect** in the context of software development is an issue, flaw, or imperfection in a software product that causes it to produce incorrect or unexpected results, or to behave in unintended ways. Defects can arise from errors in requirements, design, coding, or testing and need to be identified, tracked, and resolved to ensure the software functions correctly and meets user expectations. **What is a Manual Testcase?** A **manual testcase** is a set of documented instructions that describe the steps to be performed manually to verify whether a particular feature or functionality of a software application is working as intended. Manual test cases are used by testers to ensure that the software meets the specified requirements and to identify any defects or issues. **What is an automation Testcase?** An **automation testcase** is a predefined script or set of instructions that are executed by an automated testing tool to verify the functionality, performance, and other aspects of a software application. Automation test cases are designed to be run without human intervention, allowing for efficient, repeatable, and consistent testing. **What is an Object?** An **object** refers to any element within the user interface (UI) of the application under test that can be interacted with during the execution of automated test scripts. These objects are typically controls or components such as buttons, text fields, drop downs, checkboxes, links, and other elements that users interact with on a web page or application interface. **What is an Object Inspector?** An **object inspector** is a tool used in automation testing to identify and capture the properties and attributes of UI elements (objects) within an application. These tools help testers and developers to understand the structure of the application's UI and to create reliable and maintainable automated test scripts by accurately identifying the elements to interact with. **What is an Action?** An **action** refers to any operation or command that is performed on a UI element (object) within the application under test by the automated test script. Actions simulate user interactions with the application to verify its behaviour and functionality. These actions are essential for creating meaningful and effective automated test cases. **What is a Function?** A **function** in automation testing is a reusable block of script that performs a specific task or set of tasks, such as interacting with a UI element, verifying conditions, or performing calculations, and can be called upon multiple times within different test cases to enhance modularity and reduce redundancy. **What is Record & Playback?** **Record & playback** is a feature in automation testing tools that allows testers to capture their interactions with an application and automatically generate test scripts based on those interactions. These scripts can then be played back to reproduce the actions, helping to automate the testing process without manually writing code. **What is Data Environment?** A **data environment** refers to a controlled setup that contains the necessary data and configurations to effectively test an application. This environment mimics the data conditions that the application will encounter in production or any other environment, allowing testers to validate functionality, performance, and other aspects under realistic scenarios. **What is Continue on Failure?** **Continue on Failure** is a setting or feature in automated testing that allows the test execution to proceed even if a particular test step or case fails. This approach ensures that the remaining test steps or cases are executed, providing a comprehensive assessment of the software's overall functionality and identifying all potential issues in a single test run. **What is Code Editor?** A code editor is an Integrated Development Environment (IDE) that allows users to create custom actions aimed at achieving specific goals. These custom actions, once created in the code editor, can be used within the actions of a test case. **What is Data Generation?** **Data generation** is the process of creating artificial data that mimics real-world data sets. This data is generated algorithmically adhering to standards such as Boundary value analysis and equivalence class partitioning and is used for testing, and validating software applications. Synthetic data is particularly useful when real data is scarce, expensive, or sensitive due to privacy concerns. **What does Obsolete Test Case mean?** **Obsoleting a testcase** refers to the process of marking a test case as no longer relevant or valid for the current testing needs. This can happen for various reasons, such as changes in the application's functionality, updates in requirements, or the introduction of new features that render the test case outdated. Once a test case is obsoleted, it is typically archived or removed from the active test suite to ensure that the testing efforts remain focused on current and relevant scenarios. **What are Parameters?** **Parameters** are variables that are used to pass different values to test scripts, allowing the same test case to be executed with multiple sets of data. This helps in creating data-driven tests where the test logic remains the same but the input data changes. Parameters enhance the flexibility, reusability, and coverage of automated tests by enabling testers to run a wide range of scenarios without duplicating the test code. **What is Test Data?** **Test data** refers to the information and input values used in testing software applications. It is essential for validating the functionality, performance, and reliability of the software. Test data can include a wide range of data types, such as numbers, text, dates, and more, and it is used to simulate real-world scenarios during testing. **What are Runtime Parameters?** A **runtime parameter** is a variable that is passed to a test script or program during its execution, rather than being hard-coded or predefined. These parameters allow the test or program to be more flexible and adaptable by enabling it to accept dynamic values or configurations at runtime. **What is a Test Step?** A **test step** is a specific action or instruction within a test case that a tester or an automated script performs to verify a particular aspect of the software application's functionality. Each test step includes details on what needs to be done, how it should be done, and what the expected outcome should be. Test steps are the building blocks of a test case, and they guide the tester through a sequence of actions to validate the behavior of the application. **What is a Screenshot?** A **screenshot** in an automation testcase is an image capture of the application's user interface at a specific point during the test execution. Screenshots are used to visually document the state of the application at various stages of the test, helping to verify that the application is displaying the correct information and behaving as expected. **What does 'Skip' in automation test case mean?** **Skip** refers to the practice of deliberately not executing a particular test or test step. Skipping a test can be done for various reasons and is usually indicated in the test results, often marked as "skipped" or "not executed." **What are object properties?** **Object properties** in an automation testcase refer to the specific attributes or characteristics of a user interface (UI) element that are used to uniquely identify and interact with that element during the execution of automated tests. These properties enable the automation tool to locate the elements within the application's UI and perform the necessary actions, such as clicking a button, entering text, or verifying the element's presence and attributes. **What is Self-Healing?** **Self-healing** in the context of automation testing refers to the capability of automated test scripts to automatically detect and adapt to changes in the application under test without human intervention. This feature helps maintain the robustness and reliability of test scripts, especially in environments where the application is frequently updated or changed. **What is parameterisation of objects?** **Parameterisation of objects** in automation testing involves using parameters in the object to dynamically define the properties of the objects. This technique allows test scripts to be more flexible and reusable by enabling the same script to interact with different UI elements based on the parameters provided. **What is Intelli-Sense?** Intelli-Sense in SimplifyQA is a powerful feature that enables users to seamlessly convert manual test cases to automated test scripts and vice versa without writing any code. This script less conversion allows users to maintain both versions within a single test case, providing flexibility and enhancing the efficiency of the testing process. With Intelli-Sense, testers can effortlessly switch between manual and automated testing, ensuring comprehensive coverage and adaptability to various testing scenarios. **What is a Suite?** A **suite** to a collection of test cases grouped together for execution. Test suites are used to organise tests in a way that makes them easier to manage, execute, and analyse. They can be organised based on functionality, features, test types, or any other logical grouping that makes sense for the project. **What is Execution Plan?** An **execution plan** in testing is a structured schedule that outlines how and when test cases will be executed to ensure comprehensive test coverage and timely completion. In SimplifyQA, an execution plan allows tests to be assigned to specific testers, ensuring that all necessary tests are executed efficiently and thoroughly. **What is Workflow Builder?** A **workflow builder** in software testing is a tool or feature that allows users to create, visualise, and manage the sequence of testing activities and processes. It helps in defining and organising the flow of tests and related tasks to ensure a structured and efficient testing process. In SimplifyQA, the workflow builder enables users to create workflows like flow charts using tests across projects. This visual representation helps in understanding and managing the testing process more effectively. **What is Scheduler?** A **scheduler** is a feature that automates the execution of test cases at specified times or intervals. It allows testers to define when and how often tests should run, enabling continuous testing and integration practices. **What is Pipeline?** Pipelines are essentially a groups of test cases or suites configured to automatically run whenever there is a build trigger on a specified branch or a job in the CI/CD tool. By automating these steps, pipelines help teams reduce errors, improve efficiency, and accelerate the software development process. # Search/Global Search SimplifyQA offers a robust search system to help you locate specific information within your workspace. Here are the different search options available: 1. Global Search 2. Advance Search 3. Table Column Search 4. Column Filter 5. Column Sort 6. Add/Remove Columns These functionalities provide several benefits- users can quickly find the relevant information within the tables by searching, filtering, sorting the specific columns. # How to use global search? Think of this as your search buddy for finding anything across all the modules within your workspace. Enter your search keyword in the designated search bar, and SimplifyQA will return results for relevant searches for all the modules in the same way. ### How to search in table? Global search would be available in all the module in SimplifyQA at the right top corner. To get the desired filtered information enter the search keyword in the search box and the searched data would be displayed in the table as shown below.

Global Search

{% hint style="info" %} Only the columns added to the table would be subject to the keyword being searched. Additionally, global search is only applicable to tables; it cannot be used on trees or any other part of the same page. {% endhint %} # How to use advance search? ## How to use advance search? **Advanced Search** is a powerful feature that allows users to perform detailed and specific searches within the system. It enables you to refine your search criteria using various filters and parameters, ensuring to quickly and accurately find the information or items you need. You can use advance search when you want to search with multiple keywords and save the search criteria as a filter. Global search would be available on the top right corner in all the modules. Let's walk through the different parts of the window:
* **Key:** The key dropdown menu lists different attributes of filters that you can use to filter your search results. You can select the field/key name using which you need the searched information. * **Condition:** The condition dropdown menu lists different operators that you can use to filter your search results. Conditions appear based on the data type of the key selected in the first field. * **Value:** Value field allows you to enter the keyword which you want to search. If the selected key in the first field has a range of value or options, those options would be displayed here and you can choose the value to apply the desired keyword. * **AND/OR:** This functionality allows you to combine multiple filter criteria. * **AND:** Narrows your search results to items that meet all specified conditions. * **OR:** Broadens your search results to items that meet any of the specified conditions. Once you have specified the desired search criteria in this advance search section, click on '**Apply**' button to apply the filter ans get the search result.
On click of '**Cancel'** button, applied search would be cleared and the search component closes. Clicking on '**Reset'** option would clear the search added, but you would remain in the same screen. **How to save applied search filters?** You can specify the search criteria in the advance search as explained in the above section. To save the applied filter, provide a name in the '**Filter Name' field** and click on '**Save'** icon to save it for future reference as shown below.
Once the filter is saved, you can access it in the **Saved Filter** section. **How to access the saved filter?** To use the saved filters: 1. Open advance search 2. Go to **Saved Filters** 3. Use search to search the name of the required filter 4. Choose the filter you want to use to search. Once you choose the filter from saved filters, the search criteria saved for that filter will be displayed in the search criteria section. 5. Click on **Apply** to apply the search criteria
#### How to edit the saved filter? 1. Go to **Saved Filters** 2. If you want to modify the saved filter, click on edit on the corresponding filter names. 3. Selected filter will be displayed on top. 4. Now edit the filter and save it. {% hint style="info" %} **Note:** Advance search is only applicable to tables; it cannot be used on trees or any other part of the same page. To use search on other sections use the desired search provided in those sections {% endhint %} #### How to delete the saved filter? * Go to **Saved Filters** * If you want to delete the saved filter, click on delete on the corresponding filter names.
# How to use column sort? ## How to use column sort? Wouldn't it be helpful to quickly organise your table data in a specific order? Column sorting allows you to do just that! By sorting your tables, you can easily identify trends, compare data points, and gain a clearer understanding of your information. **Sorting Your Table Columns** Here's a guide on how to sort columns in your tables: 1. **Locate the Column Header:** Identify the column you want to sort by. Look for the header row of your table and find the column name that represents the data you want to order. 2. **Click the Sort Icon:** Click on the column header, an arrow pointing up or down. This icon indicates that you can sort by this column. 3. **Choose Your Sort Order:** Clicking the sort icon will sort the table data: * **Ascending Order (A to Z or Lowest to Highest):** This sorts the data in your chosen column from the smallest value (or alphabetically for text) to the largest. * **Descending Order (Z to A or Highest to Lowest):** This sorts the data in reverse order, starting from the largest value (or Z to A for text) to the smallest. 4. **View the Sorted Data:** Your table will now be reorganised based on your chosen sort criteria. The data in the selected column will be in the order you specified. **Additional Tips for Column Sorting** * **Sort Indicators:** After sorting, your table would visually indicate the sort order using arrows within the header row. This helps you stay informed about how your data is currently organised. * **Clear Sorting:** If you want to revert your table to its original order, locate the sort icon in the column header again and click on it to view all your data. # How to use column filters? ## How to use column filters? Column filters allow you to quickly access your tables on the specific data you need. By filtering specific columns, you can easily analyse data and locate relevant information within your data set. **Applying Column Filters** Here's how to apply column filters in your tables: 1. **Locate the Column Header:** Identify the column you want to filter. Look for the header row of your table and find the column name that corresponds to the data you want to focus on. 2. **Access the Filter Menu:** Click on the filter icon located next to column search in the header. This action will open the column filter menu. 3. **Select Your Filter Criteria:** The filter menu will present you with various options depending on the data type of your column. 4. **View the Filtered Results:** Your table will now only display rows that match your chosen filter criteria. **Additional Tips for Using Column Filters** * **Combine Filters:** You can often apply filters to multiple columns simultaneously to achieve even more precise results. * **Clear Filters:** To remove a filter and see all your data again, locate the filter icon with red indicator in the column header and remove the the filter. * **Search within Filters:** Search within the list of available options for faster selection, especially for large datasets. # Add or remove columns ## Add or remove columns Adding or removing the columns from table can be done as described below: **Adding Columns** 1. **Locate the Columns:** Navigate to column preference available for table and identify the column you want to add to the table.
2. **Enable the Desired Column:** Enable to toggle option against the column you want to add to your table. 3. **View the Data:** Your table will now only display column that that you've chosen. **Removing Columns** Removing unwanted columns from your table can be done through the following steps: 1. **Select the Column:** Navigate to column preference available for table and identify the column you want to remove from the table. 2. **Delete Column:** Turn off the toggle option against the column you want to remove from your table. **When to Add or Remove Columns** * Add columns when you need to include new data categories or attributes relevant to your analysis. * Remove columns when they contain data which is irrelevant for you or duplicate information present in other columns. {% hint style="info" %} All the custom fields added would be displayed in the column preference for you to add or remove columns and get desired information. {% endhint %} # Rich Text Editor The rich text editor empowers you to create visually engaging and informative content within your application. It provides a user-friendly interface that goes beyond basic text editing, allowing you to format, style, and structure your content like a pro. The rich text editor offers a variety of tools to enhance the appearance and readability of your text: * **Font Styles:** Bold, italicise, strikethrough or underline text to emphasise important points or differentiate content sections. * **Font Size and Color:** Adjust the size and color of your text to create a hierarchy and improve visual clarity. * **Text Alignment:** Align your text left, right, or justify to achieve a polished look and guide the reader's eye. * **Bulleted and Numbered Lists:** Organise your content logically and improve readability with bulleted or numbered lists. * **Text Indentation:** Indent paragraphs to create visual separation and improve readability. * **Hyperlinks:** Embed links within your text to direct readers to relevant webpages or resources. * **Tables:** Create tables to organise complex data and improve information presentation. * **Images and Videos:** Embed images directly into your content to add visual interest and break up text.
# Import & Export Users can choose to export the listed data to excel for further analysis, for sharing or for offline access and backup. In tool, all modules that have list view allow data to be exported to excel. ### How to export selected data? * Select the number of rows by clicking on the checkbox in the table of list view * Click on 'Select all' checkbox that is available at the table header. Irrespective of what is loaded on the screen, all the rows of the data would be exported * Click on column preference icon \, toggle the columns that need to be exported. All the columns that are added for viewing would be exported. * Apply column search, global search or advanced search to filter out the required data and export {% hint style="info" %} *Note: Few default data would be exported along with the artefact even if they are not available in the list view. For example, when Test Case is exported, Step description and expected results would get exported even if they are not visible in List view table.* {% endhint %}
Who can export data? Users who have Add/Edit privileges to Module, can export the data of that module, in assigned Projects.
Is there any limitation on the number of rows that can be exported? Yes, a maximum of 5000 rows of data can be exported in any module. Anything beyond please reach out to
Can I export and Import back to other project in SimplifyQA? Yes, user can export and import artefacts between different projects in SimplifyQA.
Is there anything that cannot be exported along with the artefact? Emailers, Comments, history cannot be exported.
# Learn how to import/export Test Cases # Learn how to import/export Test Data # Add Attachments Adding attachments allows you to incorporate relevant documents, images, or other files into your work within the application. This can significantly improve clarity, provide additional context, and streamline information sharing. **Attaching Your Files** Once you've located the attachment feature, follow these steps: 1. Attachments would be available in most of the modules. **Click the 'Upload' Button.**
2. **Browse Your Files:** A file selection window will appear. Navigate to the location on your computer where the file you want to attach is stored. 3. **Select the File:** Click on the desired file to choose it for attachment or 4. **Drag and Drop:** Drag the file to the upload file section in the application and drop it. 5. **Verify:** Verify the selected file is uploaded in attachments section. {% hint style="info" %} **Note:** * **File Size Limits:** Be aware that 20MB would be the limitations on the size of files you can upload. * **Supported File Types:** Attachment feature in each module would have the list of files supported, make sure the file you want to attach is compatible with the attachment feature in the specific module before attempting to upload it. {% endhint %} #### Delete uploaded attachments * Once you've located the attachments, hover on the attachment uploaded. * Click on delete icon on corresponding attachment. * Confirm the deletion in a flash message. # Add Linkages Linkages allows you to establish connections between related artefacts. This helps you visualise dependencies, track work progress efficiently, and gain a broader understanding of your project landscape. For Example, * An artefact may clone from another * An artefact may duplicate another * An artefact may block another Your administrator can customise the linkages, refer [configure page layouts](https://simplifyqa-2.gitbook.io/untitled/~/changes/qu0MlXLhLdZ5ewq5nu9n/admin-controls-and-configurations/manage-projects-and-users/configure-page-layout) to know how to create and customise linkages. You will be able to find linkages in modules like Epic, Feature, User story, Task, Defect, Test case and Function. You can link these artefacts based on the linkages available. Below is how it looks when linkage is created between user story and task. ss **how to edit and delete linkages?** # Add Comments Comments are a powerful tool for collaboration and clarification within the application. They allow you to leave notes, ask questions, or provide feedback directly on specific parts of your work. This can streamline communication, keep track of discussions, and ensure everyone is on the same page. Once you've located the commenting feature, follow these steps: 1. **Write Your Comment:** Type your comment in the rich text box which is dedicated for comments. 2. **Mention Specifics (if applicable):** If your comment refers to a particular part of the work, you might be able to highlight or tag that specific element within your comment for better clarity. 3. **@ Mention People (if applicable):** Mention specific users by their usernames within your comment to directly notify them and involve them in the discussion. 4. **Post Your Comment:** Click a "Comment" button to finalise and add your comment. **Viewing and Replying to Comments** Comments are typically displayed alongside the same comment section in all the modules. You can view existing comments and participate in discussions by: * **Clicking on the Comment Icon or Indicator:** In board, comment icon will reveal the comment text and any replies. * **Replying to Comments:** Tool allow you to reply to existing comments, threading the conversation for easy reference. * **Delete Comments:** If a comment is no longer relevant and if you are the commenter you will be able to delete it. **Using Comments Effectively** * **Clear and Concise Communication:** State your comment or question clearly and directly to avoid confusion. * **Tag Relevant People:** Use the "@" mention feature (if available) to notify specific users who need to be involved in the discussion. * **Use Comments for Feedback and Discussions:** Comments are a great way to provide constructive feedback, ask clarifying questions, and brainstorm ideas collaboratively. # Manage Cards in board view Cards are the building blocks of your Kanban board, representing individual tasks or work items. This section will guide you on how to effectively utilise cards to manage your workflow. You will come across boards and cards in most of the modules in the tool. For Example, Below is the skeleton of a task card.

Example: Skeleton of Task Card

You will be seeing, Task ID, Status, Sprint Name, Task Name, Start Data & End Date. If any of the work item is overdue, then you will be seeing overdue details on the card. On hover of the card, you'll be having below options:
* **Assign:** Allows you to choose the desired members from the list users and assign the task to a person who is responsible for completing the task. * **Add Comments:** Allows you to leave notes, ask questions, or provide feedback directly on specific parts of the work. * **Copy Link:** Quickly share content by copying its unique link. A single click copies the link to your clipboard, ready to be pasted wherever you need. #### How to Use Drag and Drop Drag and drop is a core feature of Kanban boards, allowing for intuitive and efficient workflow management. * **Select a card:** Click and hold on the card you want to move. * **Drag the card:** Move the mouse while holding the card to your desired column. * **Drop the card:** Release the mouse to place the card in the new column.
Cards typically flow from left to right across your board, representing progress through your workflow. * **Forward Movement:** Easily drag and drop cards to the next column as work progresses. * **Backward Movement:** While generally discouraged to maintain workflow clarity, there might be instances where a card needs to move backward. In such cases, provide a clear explanation in the card's comments section about the reason for the backstep. #### Additional Tips * **Visual feedback:** Pay attention to visual cues, such as highlighted drop zones while using drag and drop, to guide your card placement. * **Keep Cards Up-to-Date:** Regularly update card information to reflect the current status, effort burnt, etc. * **Visual Cues:** Utilise card colors, sizes, or icons to quickly identify card types or priorities. # Configure Watchlist A Watchlist is a feature designed to keep you informed about the progress of the projects day to dat activities. By adding users to your watchlist, you can receive regular updates on their project involvement and progress. #### Configure Emailer Settings Adjust settings to specify the specific SDLC events that interest you in Emailer Settings section. #### Managing your Watchlist Watchlist would be available in most of the modules to received emails on any activities or updates. Locate the icon as shown in the below screenshot in any module where you would like to receive email notification.
**Add users to watchlist** * **Navigate to Users Tab** * **Search for Users:** Utilise the search bar to find specific users. * **View Watchlist Members:** Access your watchlist to see the list of included users. * **Select Users:** Check the boxes next to the users you want to add to your watchlist. **Add non-users to watchlist** * **Navigate to Non-Users Tab** * **Search for Users:** If a non-user is already added to the list, utilise the search bar to find specific users. * **Specify the emailID:** Provide the emailID of the non-user and click on '+' button or 'CTRL+Enter' to add the new user to watchlist.
* **Select Users:** Check the boxes next to the added users you want to add to your watchlist. **Add groups to watchlist** * **Navigate to Groups Tab** * **Search for Groups:** If a group is already added to the list, utilise the search bar to find specific group. * **Add New Group:** Click on the '+' icon in group tab.
* **Specify the Group Name** * **Select Users:** Check the boxes next to the added users and non-users you want to add to the group.
* **Select Group:** Check the boxes next to the added group to add the group to watchlist. * **Remove User from Group:** To remove users from group, check the boxes next to the users and non-users in the groups tab and click on delete icon.
Once users are added to your watchlist, you will receive regular updates about their project activities, including: * Task assignments * Task updates * Milestone completions * Test Execution Status * Reports and more By effectively using Watchlists, you can stay informed about the progress of your team and make informed decisions. # Track Edit History The History module provides a chronological record of changes made to a specific item or record. Edit history will be available in most of the modules, to track the changes made by the users. Once you've located the history icon: * **Timeline View:** Displays a sequential list of updates, with the most recent at the top. * **User Information:** Indicates who made the changes, including their name and timestamp. * **Description of Changes:** Provides a summary of the modifications made in each update.
You can filter the history details by 'User' and 'Interval' to get desired information
# Hierarchy Tree A tree structure is a hierarchical way to organize and visualize data, resembling an upside-down tree with a root node at the top and branches extending downwards. #### Common Tree Structure in SimplifyQA * **File System:** Represents files and directories in a hierarchical manner. Ex: Scenarios * **Organisational Chart:** Depicts the hierarchy of requirements within a project. Ex: Requirement Management * **Category and Subcategory:** Organises artefacts into categories and subcategories. Ex: Modules and Sub-modules #### Interacting with Trees * **Expanding and Collapsing:** Open or close branches to reveal or hide child nodes on click of expand and collapse icon in each node in tree. * **Searching:** Find specific nodes within the tree using search functionality by providing the desired search keyword. To get more accurate result and find the specific nodes, enable the node in which you want the system to search as shown below.
For Example, in requirement management - root node would be Epic and child would be Feature and feature would have user story. If you want to only get the search result for user story, enable user story toggle in the 'Search By' field and the search keyword provided by you would be applicable only for the specified node.
* **Selecting Nodes:** Choose individual nodes for various actions. On right click on the selected node you will be getting more options for editing, adding/creating child node, delete, drag & drop and more.
* **Dragging and Dropping:** Rearrange nodes within the tree structure. Identify the nodes which you want to move. You can either select individual nodes or multiple nodes (using SHIFT and CTRL keys) and drop it to the valid destination node.
# Shortcut keys in Test Management # Understanding the 'My Profile' Section The My Profile section in SimplifyQA acts as a centralized hub for managing your account settings, preferences, integrations, and security. This area is accessible from the user menu and is divided into three key categories: * Switch to Admin * Manage Account * Settings. **1. Switch to Admin** If your user role has been granted the appropriate privileges, you will see the "Switch to Admin" option. This allows you to enter the admin mode and access organization-wide configurations and controls.\ This feature is typically used by project owners to [manage user roles, privileges, and other administrative tasks.](/admin-controls-and-configurations) **2. Manage Account** This section focuses on user-specific settings and includes the following subsections: * My Profile:\ Update your personal details such as name, email, and contact information. Keeping this information current helps ensure better collaboration and notifications. * Change Password:\ Use this option to change your current password securely. It's a good practice to update your password periodically for security. * Project Management:\ Configure and manage third-party integrations (e.g., JIRA, Jenkins, Git) that are tied to your projects. This enables smooth CI/CD and issue-tracking workflows. * Security: * API Token Generation: Create or regenerate API tokens for accessing SimplifyQA APIs securely. * Machine Registration Token: Generate tokens for registering agents or machines. * Two-Way Verification: Add an extra layer of security to your account by setting up 2FA (Two-Factor Authentication). * File Repository:\ Access and manage files uploaded or stored within your account for use in tests and other operations.\ The **File Repository** in SimplifyQA serves as a centralized hub to upload, store, manage, and reuse files across projects and test cases. It supports various file types such as `.csv`, `.xls`, `.pdf`, `.txt`, and images, making it ideal for handling test data, reference documents, and upload/download validations. Files stored in the repository can be directly linked to test steps, enabling seamless integration into both manual and automated test scenarios. With role-based access control, only authorized users can manage or reference files, ensuring security and relevance across teams. * Themes:\ Personalise your SimplifyQA experience by selecting a preferred theme or layout. **3. Settings** The Settings tab is geared towards configuring and customizing your working environment in SimplifyQA. Here's a breakdown: * Configuration: * Action List: Customize or extend the list of predefined actions available in the test builder. * Object Template: Set default templates for identifying and working with objects. * Registration Details: Manage and update registration details. * Execution Configuration: Set defaults for test execution behavior including retry logic, timeouts, browser preferences, etc. * Custom JAR:\ Upload or manage custom JAR files that contain reusable methods, integrations, or utilities you want to use in your test cases. * Downloads:\ From here, you can download essential tools such as: * SimplifyQA Agent * Code Editor * iOS Settings:\ Configure device settings and profiles required for testing on iOS platforms. **4. Log Out** Clicking Log Out securely ends your SimplifyQA session, ensuring your data and workspace remain safe. The My Profile section empowers users with full control over their account, security, preferences, and connected tools. Whether you're updating personal info, managing integrations, or downloading tools, this area offers everything you need to configure SimplifyQA to match your workflow. # Requirement Traceability Matrix The Requirement Traceability Matrix (RTM) in SimplifyQA provides a comprehensive and visual mapping between requirements, features, user stories, test cases, and defects. This ensures end-to-end traceability, making it easy to validate that all requirements are tested and any changes are effectively managed. SimplifyQA’s RTM is particularly powerful because it visually represents these relationships in a hierarchical and interactive interface. #### **Why is RTM Important?** 1. **Ensures complete test coverage**\ Every requirement is linked to one or more test cases, ensuring nothing is left untested. 2. **Simplifies impact analysis**\ If a requirement changes, you can instantly see which test cases will be affected. 3. **Improves accountability and quality**\ Teams can verify that each business need is validated by tests, reducing missed functionality. 4. **Supports audits and compliance**\ Clear documentation of requirement-to-test mapping is crucial for regulated industries. ### Key Elements #### Project and Release Selection * Project: Select the project you are working on. * Release: Choose the release you want to analyze (e.g., "Release 5"). * Sprint Filter: Filter requirements and test cases by specific sprints (e.g., Sprint 5.1, Sprint 5.2, etc.). Multiple sprints can be selected simultaneously. **Summary Metrics** At the top of the RTM screen, summary metrics give you a quick snapshot of the testing progress: * EPICs: Total number of EPICs in the selected release (e.g., 10). * Features: Total number of features linked to EPICs (e.g., 14). * User Stories: Total number of user stories (e.g., 566). * Test Cases: Total number of test cases (e.g., 55). * Defects: Total number of defects linked to test cases (e.g., 4163). Each of these metrics is clickable, allowing users to drill down into specific items. #### Visual Traceability Graph The RTM visualizes relationships as a hierarchical graph, where: * EPICs are displayed as the top-level nodes (e.g., EP-47: Implementation of Marketplace). * Each EPIC branches into its associated Features (e.g., FT-41: Jira Integration). * Features further branch into their associated User Stories (e.g., US-754: Marketplace user login capability). * User Stories branch into Test Cases (e.g., TC-2117: Jira Plugin integration testing). * Defects can be linked to test cases. #### Detailed Drill-Down By clicking on a node (EPIC, Feature, or User Story), users can view: * Description. * Linked requirements, features, and test cases. * Execution status of test cases (Pass, Fail, Not Run). * Linked defects and their statuses. For example: * EP-47 ("Implementation of Marketplace") branches into multiple features (FT-41, FT-45, FT-50) and further into user stories and test cases. ### Key Features and Benefits * End-to-End Traceability: From EPICs to Features to User Stories to Test Cases (and Defects). * Dynamic Filtering: By Release, Sprint, and Status for precise traceability views. * Hierarchical Visualization: Easy to understand relationships and coverage. * Execution Status: Identify gaps and testing progress at a glance. * Interactive Drill-Down: Clickable nodes for details and quick navigation. ### Sample Workflow Example EP-47 (Implementation of Marketplace)\  ⬇️ FT-41 (Jira Integration)\    ⬇️ US-754 (User login capability)\      ⬇️ TC-2117 (Test scenarios for Jira plugin integration)
### Conclusion The RTM module in SimplifyQA offers a powerful and intuitive way to manage requirements and ensure complete test coverage. With its interactive, hierarchical visualization and dynamic filtering capabilities, teams can confidently validate that every requirement is fully tested—ensuring product quality and stakeholder satisfaction. # Story Studio **Story Studio** is SimplifyQA’s AI-powered workspace that enables teams to convert requirements into structured, execution-ready QA assets. By intelligently analyzing documents and inputs, Story Studio helps generate **Features, User Stories, and Test Cases**, while ensuring seamless integration with SimplifyQA’s built-in ALM modules. It is designed to accelerate the QA lifecycle while maintaining accuracy, traceability, and user control. ### **Accessing Story Studio** To access Story Studio: 1. Log in to the **SimplifyQA** application 2. From the **header menu**, select Story Studio The Story Studio workspace opens, allowing you to begin creating AI-powered QA assets.
### **Uploading or Attaching Requirements** Users begin by uploading or attaching requirements to Story Studio. Supported input sources include: * Business Requirement Documents (BRD) * Functional and Product Requirement Documents (FRD / PRD) * Figma design files * JIRA tickets * Requirement links * Plain text or unstructured inputs Once attached, Story Studio analyzes the content to understand the application’s functionality and testing scope.
### **Selecting the Generation Mode** Before generating any assets, users must choose a generation mode. The selected mode applies across Features, User Stories, and Test Cases. #### **Auto Mode** Auto Mode generates concise and optimized outputs, making it suitable for quick requirement analysis and faster asset creation. #### **Max Mode** Max Mode performs deeper analysis and generates detailed outputs, including broader coverage and edge cases. This mode is recommended for complex or enterprise-level applications. ### **Choosing What to Generate** After selecting the generation mode, users can choose the type of output to generate: * **Features** * **User Stories** * **Test Cases** While users can start at any level, generating Features first is recommended to ensure structured traceability across assets.
### **Feature Generation** When Feature generation is selected, Story Studio: * Analyzes the uploaded requirements * Identifies and extracts core functionalities * Structures them into Features * Displays the generated Features in the left-hand panel Users can review, select, edit, or rename Features as required. Selected Features serve as the foundation for User Story creation.
### **User Story Generation** From the selected Features, users can generate User Stories directly within Story Studio. * **Auto Mode** generates streamlined, well-defined User Stories * **Max Mode** generates detailed User Stories with enhanced coverage and context Generated User Stories are displayed in the workspace for review.
### **Refining User Stories Using AI Prompts** Story Studio allows users to refine User Stories through both manual edits and AI-assisted prompts. Users can: * Rephrase User Stories * Add or remove scenarios * Modify acceptance criteria * Adjust business logic All updates are applied in real time, ensuring accuracy and alignment with requirements.
### **Test Case Generation** Once User Stories are finalized, users can generate Test Cases directly from them. * **Auto Mode** generates essential test cases focused on core functionality * **Max Mode** generates detailed, end-to-end test cases covering positive, negative, and edge scenarios Test Cases are structured, reusable, and ready for execution.
### **Refining Test Cases Using AI Prompts** Test Cases can be further customized using AI prompts or manual edits. Users can: * Modify test steps * Enhance validations * Improve scenario coverage * Align test cases with application behavior This ensures test cases meet both functional and quality standards.
### **Saving Assets to ALM Modules** After review and finalization, AI-generated assets can be saved directly into SimplifyQA’s ALM modules. * **User Stories** can be saved to the **Requirement Management** module * **Test Cases** can be saved to the **Test Management** module This ensures centralized management, traceability, and seamless collaboration across teams.
### **Chat History** Story Studio maintains a complete history of user interactions and generated outputs. * Users can access previous conversations by clicking on the **History** option * Chat history allows users to revisit, review, and continue previous work without regenerating content ### **Creating a New Chat** Users can start a new interaction at any time by selecting **New Chat**. This is useful when working on new requirements, creating separate workflows, or keeping conversations independent.
### **Key Benefits of Story Studio** * Accelerates conversion of requirements into QA assets * Supports both quick and detailed generation through Auto and Max modes * Maintains traceability across Features, User Stories, and Test Cases * Integrates seamlessly with SimplifyQA’s built-in ALM modules * Provides AI-driven assistance while retaining full user control # My Board in SimplifyQA The My Board section in SimplifyQA functions as a personal task management dashboard — similar to a to-do list. It provides users with a consolidated view of all the items assigned to them across various modules. These items include: * **Tasks** * **User Stories** * **Defects** * **Execution Plans** * **Review/Approve Requests** This board helps users stay organized and track their responsibilities within a selected release and sprint context. ### Key Features 1. **View Assigned Items** Users can view all work items assigned to them, neatly categorized by type (Task, User Story, Defect, etc.), with each showing the: * Title * Status (To Do, In Progress, Done, etc.) * Due Date (if applicable) * Priority 2. **Filter Options** You can filter the view based on: * Release * Sprint 3. **Add New Items**\ Users can quickly add: * A new Task * A new User Story * A new Defect * A new Execution Plan This helps streamline work tracking from a single dashboard. 4. **Status Updates**\ Users can update the status of work items directly from My Board without navigating away simply by dragging and dropping, allowing for quick updates and seamless tracking. ### How to use My Board 1. Navigate to My Board from the left-hand panel. 2. By default, all assigned items for the current release and sprint are shown. 3. Use the filter panel on the top to refine the view by release, or sprint. 4. Click Add to quickly log a new task, defect, user story, or execution plan. 5. Track progress or update status directly from the board by clicking on the item's card. 6. Use the board daily to ensure you're aware of pending work and upcoming deadlines. ### Benefits of using My Board * Centralised view of your work * Improved personal productivity * Real-time status visibility * Quick access to item details and updates # Admin Controls & Configurations SimplifyQA provides comprehensive administrative controls that enable organizations to manage users, roles, permissions, and workspace configurations efficiently. The Admin Control Panel ensures that teams have the right access, security measures, and custom configurations to streamline their testing processes. ### Key Features of Admin Control & Configuration 1. **User Management** * Add, edit, or remove users from the SimplifyQA workspace. * Assign specific roles and permissions based on responsibilities. * Manage authentication settings for secure access. 2. **Role-Based Access Control** * Define custom roles with specific permissions (e.g., Admin, Tester, Developer). * Restrict access to sensitive modules like Defect Management or Automation Suites. * Ensure that only authorized users can perform critical actions. 3. **Workspace Configuration** * Customize project settings, naming conventions, and test case templates. * Configure the default dashboard layout for enhanced usability. * Set up notification preferences for test case updates, defects, and execution reports. 4. **Integration Management** * Connect JIRA, Jenkins, Git, and other third-party tools for seamless collaboration. * Configure API keys and webhooks for custom integrations. * Manage CI/CD pipeline integrations for automated test execution. 5. **Execution & Environment Settings** * Configure test execution environments such as local, cloud, or virtual machines. * Manage browser settings, parallel execution, and device configurations. * Enable test scheduling for automated test execution at predefined intervals. 6. **Project and Data Management** * Create and manage multiple projects under one workspace. * Define project-specific test repositories and execution parameters. * Implement version control for test cases and automation scripts. 7. **Security & Compliance** * Enforce two-factor authentication for added security. * Maintain audit logs to track changes in test cases, execution, and defects. * Control data access policies to meet compliance requirements. ### Frequently Asked Questions (FAQs)
Can I customize notifications for different users? Yes, admins can configure email and in-app notifications for test executions, defect tracking, and reports.
Is it possible to set up multiple administrators for a workspace? Yes, multiple users can be assigned Admin roles, allowing them to manage settings, integrations, and security policies.
Can I restrict certain users from deleting test cases or defects? Yes, by configuring role-based permissions, admins can restrict users from modifying or deleting test cases, defects, and other critical assets.
Can I disable access for inactive users? Yes, admins can deactivate user accounts to prevent access without permanently deleting their data.
Can I create custom fields for test cases and defects? Yes, you can define custom fields to capture additional information specific to your testing needs.
# Business Unit In SimplifyQA, the Business Unit is a logical grouping feature that helps organizations manage and segregate their testing assets, users, and project activities based on different departments, clients, or functional divisions. It acts as the top-level container under which multiple projects and user roles are organized. This feature is particularly useful for companies with multiple clients, departments, or business streams who wish to maintain data privacy, better access control, and operational clarity. ### Key Features of Business Units 1. **Segregation of Projects** * Each business unit can have its own set of projects, completely isolated from other units. * Projects created under a business unit are only visible to users associated with that unit. 2. **User Management and Access Control** * Admins can assign users to specific business units. * Role-based access within a business unit ensures that users only see and manage what's relevant to them. 3. **Data Isolation** * Test cases, defects, requirements, and execution plans are isolated per business unit. 4. **Analytics and Reporting** * Reports can be generated at the business unit level for more targeted insights. * Helps in evaluating performance and test coverage for each business division. ### Creating a Business Unit To create a new Business Unit in SimplifyQA, follow these steps: 1. **Login as Admin**\ Only Admin users have the rights to create and manage business units. 2. **Navigate to Admin Settings** * Click on your profile or settings icon in the top-right corner. * Select Admin Panel or Settings from the dropdown. 3. **Go to 'Business Unit' Section** * In the left panel of the Admin Panel, select Business Unit. 4. **Create New Unit** * Click on Create New Business Unit button. * Fill in the required details: * Business Unit Name (e.g., Retail Banking, Healthcare Division, Client-X) * Description (optional, but helpful for context) 5. **Save** * Click Save to successfully create the business unit.
### Managing Business Units * **Edit or Delete a Business Unit** * From the list of existing units, click on the View Details icon next to the desired unit. * Note: Deleting a business unit will also remove all its associated projects and data. Proceed with caution. * **Assign Users to a Business Unit** * Navigate to the Project section. * Select a project and assign them to the appropriate business unit(s). * A user can be part of multiple business units but will only have access based on their role in each.
* **Switch Between Business Units** * If a user is part of multiple units, they can switch units using the dropdown selector typically located at the top of the dashboard.
### Accessing Business Unit on the Landing Page Users can view and switch between their assigned Business Units directly from the landing page, provided their role has the appropriate privileges. **Steps to Enable Business Unit Visibility on Landing Page:** 1. **Go to Project Settings** * Navigate to the Project Settings from the top menu or the settings icon. 2. **Access Roles & Privileges** * Click on Roles & Privileges. 3. **Select the Respective Role** * Choose the role for which you want to enable access (e.g., QA Engineer, Project Manager). 4. **Enable the ‘Show Project’ Privilege** * Under the section Project & Release Management, enable the checkbox for “Show Project”. * This allows users with that role to view the Business Unit and project details directly on the landing page. 5. **Save Changes** * Click **Save** to apply the updated role privileges. Once this is enabled, users will see a dropdown or listing of available Business Units on their dashboard, making it easier to navigate and access the relevant projects. ### Use Case Scenarios * **Multiple Clients**:\ An organization serving different clients can create separate business units for each client to keep their projects, test cases, and reports completely isolated. * **Department-wise Testing**:\ If internal QA teams handle testing for various departments like HR, Finance, IT, and Operations, each department can have its own business unit for better organization and visibility. * **Multi-Domain Projects**:\ For companies that handle multiple business domains (e.g., Banking, Insurance, Retail), setting up business units per domain can streamline project and user management. * **Offshore-Onshore Teams**:\ In a global delivery model, you can create business units for offshore and onshore teams to manage access, reporting, and work ownership. * **QA Service Providers**:\ For QA consulting or service companies, business units can be used to create client-specific environments ensuring data privacy and independent project execution. ### Frequently Asked Questions (FAQs)
Can a user access multiple business units? Yes, a user can be part of multiple business units but must be assigned accordingly by the admin.
Is it possible to restrict visibility of test cases or defects by business unit? Yes, all artifacts in SimplifyQA are scoped to their respective business units, ensuring data isolation.
# Manage Projects & Users A project represents a structured framework used to plan, organise, automate, execute, and monitor a specific goal or deliverable within defined constraints such as time, budget, and resources. Projects enable teams to collaborate efficiently, track progress, and manage project-related tasks systematically. # Introduction to Projects in SimplifyQA A Project in SimplifyQA serves as the centralised workspace where teams manage their test cases, requirements, test executions, automation scripts, and reports in an organised manner. It helps teams structure their testing process, ensuring better collaboration, traceability, and efficiency across the Application Lifecycle Management (ALM) process. ### Key Uses of Projects in SimplifyQA * **Multiple Projects for Different Applications:** Manage multiple projects simultaneously, each dedicated to a specific application, module, or release cycle. * **Team Collaboration & Access Control:** Assign roles and permissions to team members, ensuring controlled access to test artefacts. * **Traceability Across Testing Lifecycle:** Link test cases, user stories, defects, and requirements to track progress and dependencies efficiently. * **Organised Test Management:** Keep all test assets (test cases, scenarios, data, automation scripts, and reports) within a single workspace. * **Environment-Specific Testing:** Maintain separate test configurations for different environments (QA, Staging, Production, etc.) within a project. * **Project-Specific Reports & Dashboards:** View customised insights, execution trends, and test results specific to each project. * **Parallel Execution Across Projects:** Run tests across multiple projects simultaneously, optimising test execution efficiency. # Create Project and Invite Users This section provides instructions on how to create a new project within the SimplifyQA platform. ### How to create a Project? **Prerequisites:** * You must have an active SimplifyQA account with admin permissions to create projects. Once you are ready with the pre-requisites, follow the below steps to create new project. 1. **Log in to SimplifyQA:** * Open your web browser and navigate to the SimplifyQA login page. * Enter your email address and password, then click the "Log In" button. 2. **Navigate to Admin Panel:** * Open "Manage Accounts" and click "Switch to Admin". 3. **Navigate to the Project List:** * On the left-hand side of the screen, you will see a navigation menu. * Click on the "Projects" option to view the list of existing projects. 4. **Create a New Project:** * In the top right corner of the project list, click on the **"+ Project"** button. * In the modal dialog, provide the following information: * **Name:** Enter a unique name for your project. * **Description:** Provide a brief description of the project's purpose. * Once you have entered the required information, click the "Create" button. * The new project will be created and added to the project list.
**Additional Notes:** * Project names should be descriptive and easy to understand. * Project descriptions should be concise and informative. * You can edit or delete projects from the project list as needed. ### How to invite users to a project? **Prerequisites:** * You must have an active SimplifyQA account with admin permissions to invite users to projects. * You must know the email addresses of the users you want to invite. Once you are ready with the pre-requisites, follow the below steps to invite users to a project. 1. **Log in to SimplifyQA:** * Open your web browser and navigate to the SimplifyQA login page. * Enter your email address and password, then click the "Log In" button. 2. **Navigate to Admin Panel:** * Open "Manage Accounts" and click "Switch to Admin". 3. **Navigate to the Project List:** * On the left-hand side of the screen, you will see a navigation menu. * Click on the "Projects" option to view the list of existing projects. * Select the project to which you want to invite new users. 4. **Invite Users:** * On the project details page, locate the "Invite Users" section. * Use the search box to find the user you want to invite to the selected project.
* The user you wish to invite won't be on the list if they aren't already a SimplifyQA user. Press 'ENTER' after entering the user's email address to invite the new user.
* You can also search for users by their name or username. 5. **Assign Roles (Optional):** * Default Role as configured in ['Roles and Privileges'](/admin-controls-and-configurations/manage-projects-and-users/project-settings/manage-roles-and-privileges) would be assigned to all users by default. Note that you can configure Roles and privileges and default settings in ['Manage Roles and Privileges'.](/admin-controls-and-configurations/manage-projects-and-users/project-settings/manage-roles-and-privileges) * You can optionally change the default role assigned to the invited users. * Select the desired role from the dropdown menu next to each email address.
6. **Send Invitations:** * Once you have entered the email addresses and assigned roles (if applicable), click the "Invite Users" button and click on "Save Button". * The invited users will receive an email invitation with a link to accept the invitation and join the project.
{% hint style="info" %} **Note:** Invited users will initially be in a "Pending Verification" state. Once they accept the invitation and complete account setup, their status will change to "Active." Users who are no longer active will be marked as "Inactive." {% endhint %} {% hint style="info" %} **Additional Notes:** * Invited users will need to create a SimplifyQA account if they don't have one already. * Once invited users accept the invitation, they will be added to the project and will be able to access its resources and collaborate with other team members. {% endhint %} ### How to assign Roles to multiple users? * Once you have entered the email addresses to invite multiple users, select the "Role" from the dropdown next to "Invite Users" search box. * The role selected from this dropdown would be assigned to all the users selected in the "Invite Users" search box. * Once you have entered the email addresses and assigned roles (if applicable), click the "Invite Users" button and click on "Save Button". * The invited users will receive an email invitation with a link to accept the invitation and join the project.
{% hint style="info" %} **Additional Notes:** * Ensure that you select the appropriate roles for each user based on their responsibilities and permissions within the project. * If you need to modify roles for users who have already been invited, you can do so from the user management section. {% endhint %} ### How to remove users from the project? **Prerequisites:** * You must have an active SimplifyQA account with admin permissions to manage users in projects. Once you are ready with the pre-requisites, follow the below steps to invite users to a project. 1. **Log in to SimplifyQA:** * Open your web browser and navigate to the SimplifyQA login page. * Enter your email address and password, then click the "Log In" button. 2. **Navigate to Admin Panel:** * Open "Manage Accounts" and click "Switch to Admin". 3. **Navigate to the Project List:** * On the left-hand side of the screen, you will see a navigation menu. * Click on the "Projects" option to view the list of existing projects. * Select the project from which you want to remove users. 4. **Remove Users:** * On the project details page, locate the "Invite Users" section. * Find the user(s) you want to remove from the list. * Select the checkboxes next to the names of the users in the user list. * Click on the **"Remove users"** button located next to the "Invite Users" button. * This will open a modal dialog confirming the removal.
5. **Confirm Removal:** * Review the list of users to be removed. * Click the "Confirm" button in the modal dialog to proceed with the removal. {% hint style="info" %} **Additional Notes:** * Removing a user will revoke their access to the project and its resources. * Once removed, users will no longer be able to view or contribute to the project. * You can remove multiple users at once by selecting the checkboxes next to their names. {% endhint %} ### How to delete a project? 1. **Delete the Project:** * On the project details page, select the project you want to delete by clicking on the checkbox next to project names. * Select the "Delete" icon in the header.
* A confirmation dialog will appear asking you to confirm the deletion. * Click the "Confirm" button in the confirmation dialog. {% hint style="info" %} **Additional Notes:** * Deleting a project is irreversible. Once deleted, all data associated with the project, including test cases, test plans, and user data, will be permanently removed. * Exercise caution when deleting projects, as it can impact ongoing testing activities and data integrity. {% endhint %} ### Resend Invitation * On the project details page, locate the "Invite Users" section. * Identify the users who are in the "Pending Verification" state. * For each user, click on the **"Resend Invite"** button located next to their email address. {% hint style="info" %} **Additional Notes:** * Resending an invitation will send a new email to the user with a new invitation link. * If a user has already accepted the invitation but hasn't completed account setup, resending the invitation will not prompt them to accept it again. * If a user is unable to access the invitation link or has any issues with the invitation process, you may need to manually add them to the project or contact the SimplifyQA support team for further assistance. {% endhint %} # Project Settings Project Settings in SimplifyQA allow teams to configure various aspects of their testing environment to align with their workflows and requirements. From customising layouts and user roles to enabling AI-powered test intelligence and defect auto-logging, the settings provide flexibility to optimise project execution. ### **Configure Layouts & Custom Fields** SimplifyQA enables users to personalise project layouts and add custom fields to capture specific data points. **Key Features:** * Modify UI layouts for test cases, defects, and requirements. * Add custom fields to match project needs (e.g., severity levels, custom statuses). * Set mandatory fields for better data consistency. ### **Configure Roles & Privileges** Roles and privileges help define user access levels, ensuring security and structured collaboration. **Key Features:** * Create and assign roles (e.g., Tester, Developer, Project Manager). * Set permissions for test execution, editing, and reporting. * Restrict access to sensitive data based on user roles. ### **Test Intelligence** AI-powered test intelligence automates object recognition and API capture while enhancing test stability. **Key Features:** * Object Recognition by JavaScript: Identifies UI elements dynamically. * Automatic API Capture: Automatically detects and records API requests in real-time while you're recording a test case. * Enable Self-Healing: AI auto-corrects broken test scripts when UI elements change. * Prioritise Object Attributes: Adjust element priority (e.g., ID, XPath) for stable test execution. ### **Effort Settings (Hours, Story Points)** SimplifyQA allows teams to estimate and track effort using different measurement units. **Key Features:** * Configure **time-based effort tracking** (hours). * Enable **story points** for Agile planning. * Align effort settings with project methodologies. ### **Configure Auto-Logging of Defects** Automate defect creation when a test case fails to improve tracking efficiency. **Key Features:** * Auto-capture failure logs and screenshots. * Link defects directly to test cases and execution results. ### **Code Editor Configurations** SimplifyQA provides an integrated code editor for writing, editing, and debugging custom code. #### **Key Features:** * Support for JAVA programming language. * Auto-suggestions and syntax highlighting. * Integration with version control systems. ### **Review & Approve Settings** Manage approval workflows for test cases, suites, and requirements before execution or closure. **Key Features:** * Enable multi-level approvals for changes. * Set up review workflows for specific user roles. * Track approval history for compliance. The Project Settings module in SimplifyQA provides a powerful way to tailor the platform to meet the specific needs of your team. Whether it’s configuring roles, enabling AI-driven testing, or streamlining approvals, these settings help optimise project efficiency and quality assurance. # Create and Manage Custom Fields ## Prerequisites: You must have an active SimplifyQA account with admin permissions to create projects. Once you are ready with the pre-requisites, follow the below steps to create and manage custom fields and change layout. SimplifyQA allows you to configure layouts and custom fields in two distinct ways: 1. **Through Project Settings:** Changes made here apply to specific projects only. 2. **Through the Admin Navigation Panel:** Changes made here apply to all projects across the customer account. ### Configure Fields and Layouts through Project Settings 1. Open the project of your choice by clicking on the arrow button on the project module. 2. **Navigating to Project Settings:** 1. You can access **Project Settings** in two way 1. Click on the **settings icon** next to the project name in the project list.
ii. Click on **"View Details"** for the project, then select the **settings icon** from there.
2. And click on **Configure Layout and Custom Fields**.
3. **Adding a Custom Field:** * Select the module you want to configure. * Choose the type of field you want to add from the options displayed on the right. You can add any kind of field here, such as text or rich text fields, a dropdown, radio button, checkbox, date, time, etc. * Drag the selected field into the desired area.
* Fill in mandatory details such as "Field Name" and "Enter Character Limit." 4. Editing, Renaming, or Moving Existing Fields * To edit an existing field, hover over it, and click the edit icon. You can rename the field here. * To reposition a field, click on the six dots next to it and drag it to the desired location. 5. **Saving the Custom Fields:** After configuring, click the "Save" button. 6. **Viewing the Custom Fields in Action** * Switch to user access and navigate to the relevant module (e.g., User Story). * Open the user story creation screen to view default and custom fields. * Custom fields are not just limited to the form; they can also be utilized in various places, such as in tables, advanced search, and the suite tree to filter trees effectively.
# Manage Roles and Privileges Roles and privileges are fundamental concepts used to manage user access and permissions. * **Roles:** A role is a collection of privileges assigned to a group of users. It defines the set of actions that users in a particular role are authorised to perform. * **Privileges:** Privileges are specific permissions granted to users, allowing them to access certain resources or perform certain actions within the system. This document provides step-by-step instructions on how to configure privileges for different roles and assign these roles to specific users within your project. ### Configuring Privileges * **Navigate to Project Settings:** Go to **Admin** > **Projects** > **\[Project Name]** > **Project Settings**.
* **Access Roles & Privileges:** * Click on the **Roles & Privileges** tab.
* **Select a Role:** Click on the desired role to view and edit its privileges. * **Manage Privileges:** * **Action:** Click on the toggle switch next to each privilege to enable or disable it. * **Permission:** The status of the permission will be indicated by a green dot (enabled) or a grey dot (disabled).
* **Set as Default:** Select the 'Set as default' to make this role the default role. * When a new user is invited to SimplifyQA or to a new project, the default role would be assigned to the user.
* **Save Changes:** Click on the **Save** button to apply the changes. ### Adding a New Role * **Navigate to Project Settings:** Go to **Admin** > **Projects** > **\[Project Name]** > **Project Settings**. Click on the **Roles & Privileges** tab. * **Add New Role:** Click on the '**+ Role'** button.
* **Enter Role Name and Description:** Provide a clear and concise name for the new role. Add a brief description to explain the purpose of the role. * **Assign Privileges:** Select the appropriate privileges from the list and assign them to the new role. * **Save Changes:** Click on the **Save** button to create the new role. {% hint style="info" %} **Best Practices** * **Least Privilege Principle:** Assign roles with the minimum necessary privileges to each user. * **Regular Review:** Regularly review and update role assignments and privileges to maintain security and control. * **Clear Documentation:** Maintain clear documentation outlining the responsibilities and privileges associated with each role in the description. {% endhint %} # Test Intelligence # Effort Settings Effort Settings in SimplifyQA allow teams to define, track, and manage the effort required for test execution and development tasks. These settings help teams estimate work, allocate resources efficiently, and track project progress using time-based or Agile estimation methods. ### **Key Effort Tracking Methods in SimplifyQA** #### **1. Time-Based Effort Tracking (Hours)** This method tracks effort in actual time units such as hours, making it ideal for projects that require precise work-hour estimations. **How It Works:** * Define effort estimates in hours when creating a test case, defect, or user story. * Track actual effort spent vs. estimated effort to monitor progress. * Generate effort reports to analyze team productivity and efficiency. **Use Case Example:** * A test case is estimated to take 4 hours to execute. * The tester logs 3.5 hours after completing the test. * The system tracks the variance and updates the overall project effort report. #### **2. Agile Effort Tracking (Story Points)** Story points are an Agile estimation technique that helps teams estimate effort based on complexity rather than exact time. **How It Works:** * Assign story points (e.g., 1, 2, 5, 8, 13, etc.) to user stories, test cases, or tasks. * Higher story points indicate more complex or time-consuming tasks. * Compare completed story points in each sprint to measure velocity (work completed per sprint). **Use Case Example:** * A simple login functionality is assigned 2 story points. * A complex payment gateway integration is assigned 8 story points. * The team completes 30 story points in a sprint, helping plan future sprints more accurately. ### **Configuring Effort Settings in SimplifyQA** 1. Go to **Project Settings → Effort Settings.**
2. **Select Effort Type:** Choose between Time-Based (Hours) or Story Points.

Time-Based (Hours)

**Time-Based:** These settings help accurately calculate and manage effort, velocity, and resource planning across sprints and releases. * **No. of Hours in a Day:**\ Defines how many **working hours** are considered in a single day.\ Example: If your team works 8-hour days, set this to `8`. * **No. of Days in a Week:**\ Sets how many **working days** your team operates each week.\ Example: For a standard Monday–Friday schedule, set this to `5`. These values are important as they determine how total effort is distributed across your team’s available capacity.

Story Points

**Story Points:** If the team estimates effort using Story Points, you can define how many hours each story point represents. This helps in converting Agile estimation into actual execution planning. Example: If `1 Story Point = 8 Hours`\ Then a task estimated at `2 Story Points` would translate to `16 Hours` of effort. This mapping helps in: * Planning test executions more accurately * Aligning Agile estimations with real-time schedules ### **Best Practices for Effort Management in SimplifyQA** * Use time-based tracking for detailed project timelines. * Leverage story points for Agile sprints and iterative development. * Regularly update actual effort to maintain accurate records. * Analyse effort reports to optimise resource allocation. Effort Settings in SimplifyQA help teams estimate and track work using both traditional (time-based) and Agile (story points) methodologies. By accurately managing effort, teams can improve planning, execution, and project delivery timelines. ### Frequently Asked Questions (FAQs)
What is the purpose of effort settings in SimplifyQA? Effort settings help teams estimate, track, and manage the effort required for test execution, development tasks, and user stories. This ensures better project planning, resource allocation, and performance tracking.
Can I switch between time-based and story point tracking? Yes, you can configure the effort tracking method based on your project requirements. However, switching mid-project may require effort recalibration.
Can I track effort for individual testers or developers? Yes, effort logs can be assigned to individual team members, helping managers track productivity at both team and individual levels.
Can I integrate effort tracking with project management tools like Jira or Azure DevOps? Yes, if SimplifyQA is integrated with Jira, Azure DevOps, or other tools, effort tracking data can be synchronized to maintain consistency across platforms.
# Configure Auto-logging of Defects Auto-logging of defects is a feature in software testing tools that automatically creates defect reports when a test case fails. This process eliminates the manual effort required by testers to document and report defects, streamlining the entire testing process. When a test case fails, the tool captures relevant information such as: * **Test case ID and name** * **Test steps and expected results** * **Actual results and error messages** * **Screenshots or logs** This information is then used to automatically create a defect, which can be managed in defect management. This document provides step-by-step instructions on how to configure the auto-logging of defects when a test case or test suite fails ### Steps to Configure Auto-Logging: 1. **Enable Auto-Logging** * **Navigate to Project Settings:** Go to **Admin** > **Projects** > **\[Project Name]** > **Project Settings**.
* Locate the option for 'Auto-Logging of Defects'.
* Enable the toggle switch to activate the feature.
2. **Set Default Fields:** * **Assignee:** Specify the default assignee for auto-logged defects. * **Status:** Set the default status for newly created defects (e.g., "Open," "New"). * **Priority:** Define the default priority for auto-logged defects (e.g., "High," "Medium," "Low"). * **Labels:** Assign default labels to help categorise and filter defects (e.g., "Functional," "Performance", "Production").
3. **Test the Configuration:** * Execute a test case or test suite. * When a test case or test suite fails verify that a new defect is automatically created in failed report and defect management with the correct information. * Auto-logged defect would be tagged in the failed step of the respective execution report or can be accessed in defect management as well.
* Check the default values for assignee, status, priority, and labels. * Ensure that the mapping between test case and defect fields is accurate. {% hint style="info" %} **Additional Tips:** * **Regular Review:** Periodically review the auto-logged defects to ensure it remains accurate and up-to-date. * Auto-logging can create duplicate defects if multiple test cases fail for the same reason. Use this feature judiciously to prevent unnecessary clutter in your defect management. {% endhint %} # Code Editor Configurations SimplifyQA's Code Editor allows users to primarily write custom methods that align with their application's specific behaviors—be it handling complex UI logic or processing external data. Additionally, with built-in Code Editor Configurations, users can seamlessly integrate their preferred code repositories, enabling a smooth development workflow while working on test scripts, automation logic, or other project-related code—directly within SimplifyQA. ### **How to Configure a Code Editor in SimplifyQA?** #### Project Level Configuration Project-level configuration allows more control over who can access and use the Code Editor within a specific project. This ensures that only relevant team members—such as automation engineers or developers—can write or manage custom methods for that project, without impacting other projects or requiring global changes. 1. Navigate to Admin Section → Project Settings → Code Editor Configurations.
2. Select the preferred platform from the dropdown menu. Common platforms that may be supported include: * Gitlab * Github * Bitbucket 3. Enter the Platform URL (e.g., the platform URL or path to link their repository with SimplifyQA.).
4. Save the configurations.
5. The code repository will now be linked to the selected project in SimplifyQA. {% hint style="success" %} Refer [Code Editor](/code-editor) to learn how to write custom methods and manage the script in repository. {% endhint %} #### Customer Level Configuration At the Customer Level, platform-wide configurations can be made for all users under an organisation by defining platform details and URLs in the admin section. * From profile, click **Switch to Admin** * Select **Layout & Custom Fields** from the left panel
* Click the **Code Editor** card and provide the **Platform** and **URL** details
### Benefits of Repository Configuration with Code Editor 1. **Centralised Access:** Work on your test automation scripts from anywhere by accessing a centralised repository linked directly within SimplifyQA. 2. **Collaboration Made Easy:** Multiple team members can contribute, review, and update scripts without code duplication or conflicts—streamlining development and testing workflows. # Configure Reviewal & Approval Workflow The Review and Approve functionality in SimplifyQA allow users to streamline their validation processes by enabling structured reviews and approvals at various project levels. This feature ensures that project artifacts undergo proper scrutiny before they are finalized or executed. ### Configure Review/Approve Settings To configure which modules require the review and approval process, the user must have Admin access, as these settings can only be managed by an administrator. 1. In Project Settings, go to Review/Approve Settings.
2. Select the modules you want to enable this feature for: * Requirement Management: Epic, Feature, User Stories * Test Management: Test Cases, Functions * Test Execution: Suites, Execution Plans, Execution Results/Reports
3. (Optional) To restrict users from executing tests without approval, enable the Restrict Execution option under Test Execution.
4. For each selected module, define the review and approval process by choosing from the following options: * **Review Options:** * Review by All: This option means that all selected users must complete their review and provide approval. * Review by Any One: A single reviewer can approve for changes to proceed. * Require Authentication: Reviewers must authenticate their credentials to finalize a review. * Require Signature: Reviewers need to provide a digital signature to complete a review. * **Approval Options:** * Approval by All: All selected approvers must approve before the item is accepted. * Approval by Any One: Approval by one approver is sufficient. * Require Authentication: Approvers must authenticate credentials. * Require Signature: Approvers must provide a digital signature.
5. Save the process. ### Assign Review and Approve Privileges The ability to review and approve is controlled through privileges. To make a user a reviewer or approver, the required privileges must be enabled under Admin settings by a user with administrative access 1. In the Admin, Navigate to the Project Settings of the desired project. 2. Click on Roles and Privileges.
3. Either create a new role or edit an existing role.
4. Enable the Review and Approve privileges from either Requirement Management, Test Management, or Test Execution
5. And Click Save to save the changes. 6. Once the role is configured, it can be [assigned to the user](/admin-controls-and-configurations/manage-projects-and-users/create-project-and-invite-users#how-to-assign-roles-to-multiple-users), granting them the privilege to review and approve items within Requirement Management, Test Management, and Test Execution modules Once the review and approval settings have been configured, project teams can begin utilizing this functionality to manage validations efficiently across modules. **Learn how to use the Review and Approve feature in practice:** [Using Review and Approve in SimplifyQA](/review-and-approve-your-test-cases-and-functions) # Grant Admin Privilege to User In this section, we'll guide you on how to grant admin privilege to user. A user can be granted admin privileges through two different modules. 1. Grant admin privilege from Project 2. Grant admin privilege from User Management ### How can a user be granted admin privileges from project? 1. **Navigate to the Project List:** * On the left-hand side of the screen, you will see a navigation menu in the admin panel. * Click on the "Projects" option to view the list of existing projects. * Select the project for which you want to grant admin privileges. 2. **Grant Admin Privileges:** * On the project details page, locate the "Invite Users" section. * Find the user you want to grant admin privileges to. * Click on the three dots (ellipsis) next to the user's name.
* A dropdown menu will appear. * Select the "Make Admin" option from the dropdown menu. * This will open a modal dialog for confirmation. * Click the "Confirm" button in the modal dialog to proceed. * Once you have assigned admin privilege, you can see the "Admin" appearing next to the names of the user in the user list.
### How can a user be granted admin privileges from user management? 1. **Navigate to the User List:** * On the left-hand side of the screen, you will see a navigation menu in the admin panel. * Click on the "User Management" option to view the list of users. * Find the user for which you want to grant admin privileges. 2. **Grant Admin Privileges:** * Click on the three dots (ellipsis) next to the user's name. * A dropdown menu will appear. * Select the "Make Admin" option from the dropdown menu.
* This will open a modal dialog for confirmation. * Click the "Confirm" button in the modal dialog to proceed. * Once you have assigned admin privilege, you can see the "Admin" appearing next to the names of the user in the user list.
{% hint style="info" %} **Additional Notes:** * Admin privileges provide extensive control over the project. Grant these permissions carefully to trusted users. * Once a user is granted admin privileges, they will have the ability to invite and remove users, assign roles, and modify project settings. * **If you need to revoke admin privileges from a user, you can follow the same steps and select the "Remove Admin" option from the dropdown menu.** {% endhint %} # Invite/Add Users to Team In this section we'll guide you on how to add users to team. A user can be add users to team through two different modules. 1. Add user to team from Project 2. Add user to team from User Management 3. Create and add user to team from Teams module ### How to add user to team from project while inviting users to project? 1. **Navigate to the Project List:** * On the left-hand side of the screen, you will see a navigation menu in the admin panel. * Click on the "Projects" option to view the list of existing projects. * Select the project for which you want to add a user to a team. 2. **Add User to Team:** * On the project details page, locate the "Invite Users" section. * Find the user you want to add to a team. * Click on the three dots (ellipsis) next to the user's name. * A dropdown menu will appear. * Select the "Add to Team" option from the dropdown menu.
3. **Select a Team:** * A modal dialog titled "Add to Team" will appear. * Select the desired team from the dropdown menu. * If the desired team does not exist, you can create a new team by clicking the "+ Create Team" button.
4. **Add User to Team:** * Once you have selected a team, click the "Add" button. * The user will be added to the selected team. ### How to add user to team from user management? 1. **Navigate to the User List:** * On the left-hand side of the screen, you will see a navigation menu in the admin panel. * Click on the "User Management" option to view the list of users. * Select the user for which you want to add to a team. * Find the user you want to add to a team in the user list. 2. **Add User to Team:** * Click on the three dots (ellipsis) next to the user's name. * A dropdown menu will appear. * Select the "Add to Team" option from the dropdown menu.
3. **Select a Team:** * A modal dialog titled "Add to Team" will appear. * Select the desired team from the dropdown menu. * If the desired team does not exist, you can create a new team by clicking the "+ Create Team" button.
4. **Add User to Team:** * Once you have selected a team, click the "Add" button. * The user will be added to the selected team. {% hint style="info" %} **Additional Notes:** * Teams can be used to organise users based on their roles, skills, or specific tasks within the project. * Users can be members of multiple teams. * Team membership can be managed by project admins. * Only active users can be added to team. {% endhint %} {% hint style="info" %} **Note:** If a user is already part of a team and is marked as inactive, all tasks and other artefacts assigned to them will remain unchanged, but new tasks cannot be assigned to the user. {% endhint %} ### How to create a team and add users from Teams module? 1. **Navigate to User Management:** * On the left-hand side of the screen, you will see a navigation menu in the admin panel. * Navigate to "User Management > Teams" option to view the list of teams. **3. Create a New Team:** * On the Teams page, click on the **"+ Team"** button.
* This will open a modal dialog titled "Create New Team." **4. Enter Team Details:** * In the modal dialog, provide the following information: * **Name:** Enter a unique name for the team. * **Description:** Enter a brief description of the team's purpose. **5. Select Users:** * In the "Select Users" dropdown, you can search for users by their name. * Select the users you want to add to the team by checking the boxes next to their names. **6. Create the Team:** * Once you have entered the team details and selected the users, click the "Create" button. * The new team will be created and the selected users will be added to the team.
{% hint style="info" %} **Additional Notes:** * Teams can be used to organise users based on their roles, skills, or specific tasks within the project. * Users can be members of multiple teams. * Team membership can be managed by project admins. {% endhint %} # User Directory and Access Control In this section let's see how to add a new user and provide access to the projects. ### How to add a new user in user management? 1. **Log in to SimplifyQA:** * Open your web browser and navigate to the SimplifyQA login page. * Enter your email address and password, then click the "Log In" button. 2. **Navigate to Admin Panel:** * Open "Manage Accounts" and click "Switch to Admin". 3. **Navigate to User Management:** * On the left-hand side of the screen, you will see a navigation menu in the admin panel. * Click on the "User Management" option to view the list of users. 4. **Create a New User:** * On the User Management page, click on the **"+ User"** button. * This will open a modal dialog titled "Create New User." 5. **Enter User Details:** * In the modal dialog, provide the following information: * **Name:** Enter the full name of the user. * **Username:** Enter a unique username for the user. * **Email:** Enter the user's email address. * **Make Admin:** If desired, select "Yes" option to assign admin privileges to the user or choose "No". * **Projects:** Select the projects to which the user should be added. * **Roles:** Select the appropriate roles for that respective project from the dropdown menu. * Click on "+" icon to add more projects to the user and select the respective roles for each project. * Default Role as configured in ['Roles and Privileges'](/admin-controls-and-configurations/manage-projects-and-users/project-settings/manage-roles-and-privileges) would be assigned to all projects by default. Note that you can configure Roles and privileges and default settings in ['Manage Roles and Privileges'.](/admin-controls-and-configurations/manage-projects-and-users/project-settings/manage-roles-and-privileges) * You can optionally change the default role assigned to the invited users. 6. **Create the User:** * Once you have entered the required information, click the "Invite" button. * The new user will be created and added to the user list. {% hint style="info" %} **Additional Notes:** * Usernames should be unique and easy to remember. * You can assign multiple roles and add users to multiple projects during the creation process. * You can edit the user details and add more projects. {% endhint %} ### Resend Invitation * On the project details page, locate the "Invite Users" section. * Identify the users who are in the "Pending Verification" state. * For each user, click on the **"Resend Invite"** button located next to their email address. {% hint style="info" %} **Additional Notes:** * Resending an invitation will send a new email to the user with a new invitation link. * If a user has already accepted the invitation but hasn't completed account setup, resending the invitation will not prompt them to accept it again. * If a user is unable to access the invitation link or has any issues with the invitation process, you may need to manually add them to the project or contact the SimplifyQA support team for further assistance. {% endhint %} ### How to delete the user? 1. **Select the User:** * Find the user you want to delete in the user list. 2. **Delete the User:** * Click on the three dots (ellipsis) next to the user's name. * A dropdown menu will appear. * Select the "Delete User" option from the dropdown menu. 3. **Confirm Deletion:** * A confirmation dialog will appear asking you to confirm the deletion. * Review the user's name and confirm that you want to delete them. * Click the "Delete" button in the confirmation dialog. {% hint style="info" %} **Additional Notes:** * Deleting a user is irreversible. Once deleted, all data associated with the user, including their projects, test cases, and other information, will be permanently removed. * Exercise caution when deleting users, as it can impact ongoing testing activities and data integrity. {% endhint %} # Configure Page Layout In SimplifyQA, configuring page layouts and custom fields allows you to tailor the platform to match your team’s workflows, data capture needs, and process requirements. These configurations help ensure that only the most relevant information is collected at each stage, making work cleaner, faster, and more standardized. Layouts and fields can be applied either **globally across all projects** (via the Admin panel) or **specifically to individual projects** (via Project Settings), giving you the flexibility to maintain both consistency and customization where needed. ## Prerequisites: You must have an active SimplifyQA account with **admin permissions** to create projects and its settings. Once you are ready with the pre-requisites, follow the below steps to create and manage custom fields and change layout. SimplifyQA allows you to configure layouts and custom fields in two distinct ways: 1. **Through Project Settings:** Changes made here apply to specific projects only. 2. **Through the Admin Navigation Panel:** Changes made here apply to all projects across the customer account. ### Configure Fields and Layouts through the Admin Navigation Panel {% hint style="info" %} Custom fields are not limited to just data entry forms. Once configured, these fields can be utilized across the platform—for example, in **table views**, **advanced search filters**, and even within the **Suite Tree** to dynamically filter test scenarios. {% endhint %} Changes made via the admin navigation panel apply globally to all projects in the customer account. You can customise the following modules for the user: Linkages, Feature, Release, Epic, and Sprint. 1. Navigate to Layout and Custom Fields by hovering over the left navigation panel > Layout and Custom Fields.
2. **Adding a Custom Field** * Select the module you want to configure. * Choose the field type from the options on the right. Types of custom fields include: * **Text:** A basic single-line text input for short strings—like names, titles, or brief notes. * **Rich Text Box:** A multi-line input that supports formatting (bold, italics, bullets, links, etc.). Ideal for detailed descriptions or formatted content. * **Number:** Accepts only numeric values. Useful for quantities, priorities, scores, or any field requiring calculation. * **Dropdown:** A single-select menu of predefined options. Keeps data consistent by limiting input to set values. * **Dependent Dropdown:** A dynamic dropdown whose available options change based on what’s selected in another dropdown. Great for hierarchical data like Country → State or Category → Subcategory. * **Checkbox:** Allows multiple selections from a list of predefined choices. Use when more than one option might apply. * **Radio:** Similar to dropdown but displayed as a list of radio buttons. Users can select only one option—faster for quick decisions. * **Date:** Captures a calendar date without a time component. Ideal for deadlines, start/end dates, or any schedule-based data. * **Date Time:** Includes both date and time selection. Useful for scheduling events, test runs, or time-stamped activities. **Clone:** Creates a repeatable section of fields. Useful when the same set of data needs to be captured multiple times—like steps in a test case or multiple approvers * Drag the field to the desired area within the module. * Fill in mandatory details such as "Field Name" and "Enter Character Limit." * Configure the field as mandatory or read-only if required. 3. **Editing, Renaming, or Moving Existing Fields** * To edit an existing field, hover over it, and click the edit icon. You can rename the field here. * To reposition a field, click on the six dots next to it and drag it to the desired location.
4. **Saving the Custom Fields:** After configuring, click the "Save" button. 5. **Viewing the Custom Fields in Action** * Switch to user access and navigate to the relevant module (e.g., Epic). * Open the module creation screen to view default and custom fields.
{% hint style="info" %} The steps and options mentioned above also apply when configuring fields through **Project Settings > Layouts & Custom Fields**. {% endhint %} # Configure your clients The client module provides a comprehensive overview of all existing clients within the product or application. It offers the ability to add new client records and effectively track and manage client. #### What details are required to add a client? As client details added here are used only for tracking Production/Support tickets for now, Client Name and Client Code are sufficient. #### What should be added as Client Code? Client code is a key to mark the defect as Production Defect. The system allows to categorize clients as either internal or external, determining which defects qualify as production defects. Clients with client codes as **0** are regarded as Internal clients and those with Client code as **1** are regarded as External clients. Only defects from External clients would qualify as Production Defects {% hint style="success" %} **Additional tips:** **External Clients:** These clients are the primary focus businesses. They are the customers who purchase products or services from the company. **Internal Clients:** These clients are individuals or departments within the organisation that rely on the work or output of your department/team. {% endhint %} #### Where do these Client names show up? Clients added within this module are accessible as options in the client field of the Defect module. When creating defects from the Support ticketing system, users can select the appropriate client from the provided dropdown list. {% hint style="info" %} **Note**: Adding Client details to defect, allows us to better categorise the defects client wise. {% endhint %} # Session Management The Session Management Module allows administrators to monitor and manage active user sessions within the system. This module displays logged-in users, their session details, active executions, and provides the ability to forcefully log users out.
1. **Viewing Active Users -** Admins can view all active (logged-in) users in a read-only table on the Sessions page. 2. **Active Executions -** * Active Executions shows the number of tasks currently running under that user session. * Users can expand the row to view details: * Execution ID * Artefact ID (e.g., TC ID, Suite ID, EP ID) * Name (TC Name, Suite Name, or EP Name) {% hint style="info" %} **Note:** * If a user created a scheduler/pipeline on another machine, execution IDs display in their session once execution starts. * Execution IDs refresh **only on page reload** (no auto-refresh). * If a user is idle, Active Executions displays as **0**. {% endhint %} 3. **Force Logout -** Admins can forcefully log users out by clicking the **Logout** button in the Action column. {% hint style="info" %} **Note:**\ The "Active Executions Terminated" section appears **only** if the user had active executions at the time of logout. {% endhint %} ### Conclusion The Session Management Module ensures that administrators can effectively monitor, manage, and control user sessions while providing clear visibility into session activity and maintaining system security. # Password settings This document provides instructions on how to configure password settings. These settings help ensure the security and integrity of user accounts by defining password policies and enforcing strong password requirements. * **Password Expiration in:** Set the number of days after which a password will expire. This forces users to change their passwords regularly, reducing the risk of unauthorised access. * **Send Reminder Email:** Specify the number of days before password expiration to send reminder emails to users. Timely reminders help users proactively change their passwords. * **Password Cannot Be Same As:** Set the number of previous passwords that cannot be reused. This prevents users from cycling through a limited set of passwords. * **Minimum Password Characters:** Define the minimum number of characters required for a password. A longer password is generally more secure. * **Maximum Password Characters:** Set the maximum number of characters allowed in a password. * **Define Password Characters:** * **Uppercase:** Specify the minimum number of uppercase letters required. * **Lowercase:** Specify the minimum number of lowercase letters required. * **Special Characters:** Specify the minimum number of special characters required. * **Numbers:** Specify the minimum number of numbers required.
{% hint style="info" %} **Additional Tips** * **Balance Security and User Experience:** While strong password policies are essential for security, it's important to balance them with user convenience. Avoid overly restrictive policies that may frustrate users and lead to workarounds. * **Regular Review:** Periodically review and update your password settings to adapt to evolving security threats and industry best practices. {% endhint %} # Dashboard Dashboards in SimplifyQA serve as powerful, interactive visual storytelling tool that help teams monitor, explore, and act on key metrics in real time. Whether you're tracking test execution trends, defect status, or automation coverage, dashboards allow you to bring your data to life through rich, customisable charts—all in one centralised view. SimplifyQA is a cloud-hosted data exploration and visualisation platform built for modern test management teams. Our fully managed service is designed to scale effortlessly across your organisation while delivering enterprise-grade security, robust reliability, and governance controls that align with your compliance needs. With SimplifyQA Dashboards, you can: * Visualise KPIs that matter to your QA and DevOps initiatives. * Create or edit dashboards as needed. * Combine multiple charts and data sources into a single, shareable canvas. * Tell persuasive stories with data to support decision-making. * Enable real-time collaboration with your team using live dashboards. Whether you're a project manager needing executive summaries or a tester wanting insight into execution stats, dashboards give you the clarity, flexibility, and visibility you need—all without writing a single line of code. # Dashboard Management in SimplifyQA Visualize, Analyze, and Align with Powerful Data Dashboards Table of Contents * [**Introduction to Dashboards**](#introduction-to-dashboards) * [**Prerequisites for Dashboard and Chart Creation**](#prerequisites-for-dashboard-and-chart-creation) * [**How to Create a New Dashboard**](#how-to-create-a-new-dashboard) * [**Creating a New Dashboard**](#creating-a-new-dashboard) * [**Editing an Existing Dashboard**](#editing-an-existing-dashboard) * [**Viewing Dashboards & Advanced Options**](#viewing-dashboards-and-advanced-options) * [**Chart-Level Options in View Mode**](#chart-level-options-in-view-mode) * [**Dashboard Management Actions**](#dashboard-management-actions) #### Introduction to Dashboards Dashboards in SimplifyQA are dynamic visual interfaces that display key data points, metrics, and charts, all in one place. They help users keep track of testing progress, project KPIs, bug trends, and automation coverage in a clear, consolidated manner. Whether you're a QA engineer, test lead, or project manager, dashboards bring visibility and actionable insights at a glance. *** #### Prerequisites for Dashboard and Chart Creation * Only users with Admin Access can create new dashboards and charts. * Regular users will only have view-only access to dashboards and charts. * If you need to build or modify dashboards, ensure your user account has been granted Admin privileges by your SimplifyQA administrator. #### How to Create a New Dashboard? SimplifyQA provides three intuitive methods to create a new dashboard, catering to different user preferences and workflows: **Method 1: Using the +Dashboard Icon on the Landing Page** * Once logged in, you'll land on the main dashboard or homepage. * On this screen, look for a '**+Dashboard'** icon prominently placed. * Clicking on this icon immediately takes you to the dashboard creation screen. * This is the fastest way to get started from the entry point of the application.
**Method 2: Via the + Icon on the Header Bar** * From any screen within SimplifyQA, locate the Global **+ icon** in the top header bar. * Click it to open a dropdown menu. * From the options listed, choose **Dashboard**. * You’ll be directed to the dashboard creation interface.
**Method 3: From the Dashboard Tab** * Click on the **Dashboard tab** from the left-hand side menu/navigation bar.
* This will open a consolidated view of all dashboards that you have created or that have been shared with you. * In the top-right corner, click the '**+ Dashboard'** button to start creating a new one.
*** #### Creating a New Dashboard 1. **Enter a Dashboard Name** * Once you're on the dashboard creation screen, on the top-right section, click on the text field there and type in your dashboard name.
2. **Adding Charts to the Dashboard** * The creation screen includes a **Content Panel** where charts can be added. * Click **+ Create a new chart** to build a new visualization from scratch. * You can also select from **existing charts** shown in a list on the right. * Use the **“Show only my charts”** checkbox to narrow down your options to just your own saved charts.
* Drag and drop charts into the main dashboard area to arrange them as needed.
*** #### Editing an Existing Dashboard 1. Navigate to the **Dashboard tab**. 2. Click on the dashboard you want to edit. 3. Select the **Edit Dashboard** button found at the top.
4. Within the editor, switch to the **Charts** tab: * Here you can view all charts that are either created by you or shared with you. * Drag & drop charts from the list into your dashboard layout. * Reorganize existing charts by dragging them to different positions.
5. **Additional Dashboard Controls:** * **Trash Icon**: Removes selected chart from the dashboard. * **Undo/Redo Arrows**: Quickly reverse or reapply the last action. * **Star Icon**: Mark the dashboard as a favorite for quick access. * **Discard Button**: Exit edit mode and cancel any changes. * **Save Button**: Finalize and save your modifications.
*** #### Viewing Dashboards & Advanced Options When you're not in edit mode, dashboards can still be customized and shared using options under the vertical ellipsis (three dots):
* **Refresh dashboard**: Select to refresh all dashboard charts (i.e. rerun chart queries and retrieve fresh data). * **Enter fulls creen:** hides the Preset menu options. * **Save as**: duplicate a dashboard, this dashboard will contain all of the same charts as the existing dashboard. This is useful to allow you to create a dashboard from an existing dashboard. * **Download**: download the dashboard as either a PDF or as an image (jpg). The files will contain only the first page of any tabs. * **Share**: * **Copy permalink to clipboard**: Copies a shareable dashboard link to your system's clipboard. * **Share permalink by email**: Launches your system's default e-mail client and composes a new message featuring your dashboard URL. * **Set auto-refresh interval**: Select to specify an automatic refresh rate for the dashboard. Options include seconds (10 or 30), minutes (1, 5, or 30), or hours (1, 6, 12, or 24). Note that this will be only applied to the current session. *** #### Chart-Level Options in View Mode Each individual chart within a dashboard also has its own options, accessible via the chart's ellipsis icon:
* Force refresh: Select to refresh the chart's data. The time duration since the last cache is also provided. * Enter full screen: View the chart in full screen mode (i.e., just the chart occupies the entire screen). Select minimize icon to return. * Edit chart: Launches the chart in the [Explore](https://docs.preset.io/v1/docs/using-preset-explore) page. * Cross-filtering scoping: opens the interface to configure which charts can be cross filtered. * View query: Launches the *View Query* panel, which displays the SQL query used for the chart. Select the Copy icon to copy this SQL code to your clipboard. * View as Table: Shows the aggregated data being displayed by the chart in a table format. * Drill to Detail: Investigate underlying data. * Share: * Copy permalink to clipboard: Copies a shareable chart link to your system's clipboard * Share permalink by email: Launches your system's default e-mail client and composes a new message featuring your chart URL * Download: * Download as Image: Downloads an image of the entire chart in JPEG format. * Export CSV: Downloads the chart's data to your system in comma-separated value (CSV) format.[ ](https://docs.preset.io/v1/docs/using-preset-explore) *** #### Dashboard Management Actions
From the Dashboard listing page, you can perform bulk actions: 1. **Edit**: Modify an existing dashboard properties.
* **Name**: The title of the dashboard. * **URL Slug**: Customize the end of the URL (slug) to a more memorable name. * **Owners**: Assign/remove edit access to the dashboard. * **Colors Scheme:** By specifying a color scheme in the dashboard properties, you can overwrite the individual chart color schemes, unifying the dashboard look and feel. * **Roles:** Roles is a list which defines access to the dashboard. Granting a role access to a dashboard will bypass dataset level checks. If no roles are defined, regular access permissions apply. * **Certification** * **Certified By:** Type in a name or group, a blue check mark will now appear next to the dashboard in the dashboard list. * **Certification Details:** adds a description that displays on hover over the blue checkmark certification icon. * **Advanced:** * **JSON Metadata**: By expanding the Advanced header, the *JSON Metadata* panel appears. This area is for power users who may wish to alter specific dashboard parameters. 2. **Delete**: Permanently remove the desired Dashboard 3. **Export**: Backup or move your dashboard to another workspace. *** Dashboards in SimplifyQA aren’t just passive data holders — they are interactive, collaborative, and essential for keeping stakeholders in sync. Use them wisely, share them strategically, and make them part of your testing and QA rituals. # How to Create Charts in SimplifyQA Turning Data into Insight: Mastering Charts in Simplify Table of Contents * [Introduction](#introduction) * [Prerequisites for Dashboard and Chart Creation](#prerequisites-for-dashboard-and-chart-creation-1) * [Starting with Datasets](#starting-with-datasets) * [Steps to Create a Chart](#steps-to-create-a-chart) * [Understanding the Chart Builder Page](#understanding-the-chart-builder-page) * [Chart Source](#chart-source) * [Metrics & Columns Panel](#metrics-and-columns-panel) * [Configuring Chart Fields](#configuring-chart-fields) * [Sampling Data](#sampling-data) * [Choosing Dimensions (X-Axis)](#choosing-dimensions-x-axis) * [Adding Metrics or Columns](#adding-metrics-or-columns) * [Running the Query ](#run-the-query) * [Visualizing the Chart](#visualizing-the-chart) * [Further Customizations](#further-customizations) * [Sharing and Exporting the Chart](#sharing-and-exporting-the-chart) ## Introduction Charts in Simplify BI allow users to visualize data in various formats such as bar charts, line graphs, pie charts, and more. These visualizations help teams make data-driven decisions by presenting information in an accessible, easy-to-read format. ## Prerequisites for Dashboard and Chart Creation * Only users with Admin Access can create new dashboards and charts. * Regular users will only have view-only access to dashboards and charts. * If you need to build or modify dashboards, ensure your user account has been granted Admin privileges by your SimplifyQA administrator. ## Starting with Datasets When creating a chart, it’s best practice to start with either a **Physical** or **Virtual dataset**. This approach provides scalability and allows you to re-use **pre-defined metrics**, making future chart building faster and more efficient. ## Steps to create a chart * In the top navigation bar, click the **"+" (plus)** icon. * From the dropdown, select **"Chart"**.
* The **"Create a new chart"** screen will open.
* In the **"Choose a Dataset"** field, click the dropdown and select your preferred dataset.
* Choose the **chart type** you'd like to use and click **"Create new chart"**.
* You can later change the chart type in the **Data** tab of the **Chart Builder**. ## Understanding the Chart Builder Page Once inside the **Chart Builder**, you can start configuring your chart’s layout, data sources, and visual parameters. ### Chart Source Located at the **top-left** of the Chart Builder, the **Chart Source** panel shows the origin of your query. * A **Pre-saved Dataset**
> ⚠️ **Note:** Editing a pre-saved dataset directly in Chart Builder will affect **all charts** that rely on that same dataset. ### Metrics & Columns Panel Below the Chart Source panel, you'll find the **Metrics & Columns** panel. This allows you to select and configure the data shown in your chart.
Use the **Search Metrics & Columns** field to quickly locate relevant data. Data types are identified with helpful icons: * **ƒ**: Function used for metrics * **Clock**: The data source's time column * **ABC**: Text data * **#**: Numeric value data You can drag and drop these fields into the **Query panel** on the right to start configuring your visualization. ## Configuring Chart Fields #### 🔎 Sampling Data Before finalizing your fields, it's a good idea to review a sample of your data. Above the **"Run a query to display results"** section, click on **"Samples"** to view a raw data preview in table format. This gives you a better understanding of what your data contains before you plot it.
### Choosing Dimensions (X-Axis) The **X-axis** (horizontal axis) can be configured in the **Query panel**: * **Temporal Data** (e.g., timestamps): * When selected, a **"Time Grain"** field appears to let you control how dates are grouped (e.g., daily, weekly, monthly). * Refer to the **Time Configurations** section for detailed guidance. * **Non-temporal Data** (e.g., category labels): * Use any categorical column to group your chart accordingly. ### Adding Metrics or Columns Once you’ve chosen a dataset and a chart type, you can begin dragging relevant **metrics** or **columns** into destination fields (such as Y-axis, filters, breakdowns, etc.). When dropped, a **pop-out window** appears automatically to let you enter details and configure settings. > 🟥 **Red Highlight Warning**\ > If you see a red highlight when dragging a metric or column: * You're adding it to an invalid field. * You've already added it elsewhere and are duplicating it inappropriately.
## Run the Query **Results Panel**\ Below the chart, there is an expandable section called **Results**. This section expands and displays the results of the fields you configured for your chart. You can easily search the results in the **search bar** or **copy your results to your clipboard** on the right.
## Visualizing the Chart Once the query runs successfully, your selected chart type will render the visualization. > Most Simplify BI charts are **interactive**. Hover over bars, lines, or pie slices to view detailed information. ## Further Customizations Simplify BI charts offer a range of customization options depending on the chart type: * Use the **Customize** tab to explore layout, colors, tooltips, labels, and more. * Try different configurations or chart types to tell your data’s story more clearly. **Tips:** * Experiment with various columns to find the most insightful combination. * Use filters or adjust time ranges to zoom in/out on specific data slices.
## Sharing and Exporting the Chart In the top-right corner (next to the **Save** button), you'll see a **three-dot "meatballs" menu** offering chart tools:
From this menu, you can: * **Download** the chart as a PNG or export data. * **In Share, Copy a permalink** to share directly. # Requirement Dashboard Guide The **Requirements & User Stories Dashboard** provides end-to-end visibility into requirement planning, execution, stability, estimation accuracy, and delivery health across sprints and releases. This dashboard enables stakeholders to: * Track requirement and user story lifecycle * Monitor sprint execution and ownership * Measure stability, quality, and estimation accuracy * Identify delivery risks early using data-driven insights It is primarily used by **Product Owners, Scrum Masters, QA Leads, and Delivery Managers** during sprint planning, reviews, and retrospectives. ### How to Use Dashboard Graphs (Common Instructions for All Widgets) Every widget on the dashboard includes a standard **three-dot (⋮) menu** in the top-right corner. These options behave the same across all graphs. * **Force Refresh:** Reloads the widget with the latest data. Always use this before reviews or release decisions. * **Enter Fullscreen:** Expands the graph for better visibility during meetings or presentations. * **Edit Chart:** Allows authorized users to modify filters, grouping, or metrics. * **Cross-Filtering Scoping:** Selecting data in one widget automatically filters related widgets for deeper analysis. * **View Query:** Displays the underlying logic or query used to generate the graph (mainly for admins/audits). * **View as Table:** Converts the graph into a table to view exact counts and records. * **Drill to Detail:** Opens individual defect records contributing to the graph. * **Share:** Generates shareable links or embedded views. * **Download:** Exports the graph or data as Image, PDF, or CSV/Excel. *** ### Status of Feature – New #### Description This widget provides a **status-wise breakdown of newly created features**, giving visibility into where features currently stand in their lifecycle.
#### Axis Details * **X-Axis:** Feature Name / Feature ID * **Y-Axis:** Count of Features #### Interpretation * Features marked **Proposed** indicate upcoming or planned work not yet started. * **In Progress** features are actively being developed. * **Released** features are completed and available for use. A healthy product typically shows: * A controlled number of proposed features * A steady movement from In Progress to Released #### Business & Operational Value * Helps product owners manage feature pipelines * Assists leadership in understanding delivery momentum * Identifies features stalled due to dependencies or prioritization issues *** ### Status of Epic – New #### Description Displays the **current lifecycle status of epics**, which usually represent large business initiatives or major functional areas.
#### Axis Details * **X-Axis:** Epic Name / Epic ID * **Y-Axis:** Count of Epics #### Interpretation * **Proposed epics** represent strategic ideas or initiatives under evaluation. * **In Progress epics** are actively broken down into user stories. * **Completed epics** signal milestone achievement. Long-running epics remaining in progress may indicate: * Scope creep * Cross-team dependencies * Incomplete story breakdown #### Business & Operational Value * Enables high-level roadmap tracking * Helps align delivery teams with strategic goals * Supports executive reporting *** ### User Story Status by Owner in a Sprint #### Description This widget shows the **distribution of user story statuses grouped by owner** for a selected sprint.
#### Axis Details * **X-Axis:** User Story Owner * **Y-Axis:** Number of User Stories #### Interpretation Each bar represents an owner and is segmented by story status such as: * Completed * Delayed * Released This visualization helps identify: * Uneven workload distribution * Owners facing repeated delivery delays #### Business & Operational Value * Improves accountability and transparency * Helps scrum masters rebalance workload * Supports performance and capacity discussions *** ### Defect Status Created for User Stories in a Sprint #### Description Tracks **defects raised against user stories** during sprint execution.
#### Axis Details * **X-Axis:** User Story ID * **Y-Axis:** Number of Defects #### Interpretation * High defect counts against a user story often indicate: * Ambiguous acceptance criteria * Incomplete requirements * Missing edge cases * Reopened defects signal quality or fix validation issues. #### Business & Operational Value * Measures requirement quality * Enables early identification of unstable stories * Strengthens collaboration between BA, Dev, and QA teams *** ### Module Stability #### Description Represents the **stability of application modules** based on how often requirements or implementations change.
#### Axis Details * **X-Axis:** Module Name * **Y-Axis:** Stability Percentage (%) #### Interpretation * **High stability (80–100%)** → Mature and well-understood module * **Low stability (<50%)** → Frequent changes, high risk #### Business & Operational Value * Guides regression testing scope * Identifies modules needing redesign or requirement clarification * Supports release risk assessment *** ### User Story Estimated vs Actual Work in Sprint #### Description Compares **planned effort versus actual effort** spent on each user story.
#### Axis Details * **X-Axis:** User Story ID * **Y-Axis:** Effort (Hours / Story Points) #### Interpretation * Close alignment = good estimation practices * Significant variance = scope creep, unplanned work, or technical complexity #### Business & Operational Value * Improves sprint planning accuracy * Enables continuous improvement in estimation techniques * Helps teams identify recurring planning issues *** ### Test Cases Created for User Stories in a Sprint #### Description Displays **test coverage per user story** by showing the number of test cases created.
#### Axis Details * **X-Axis:** Sprint / User Story ID * **Y-Axis:** Number of Test Cases #### Interpretation * Higher test case count generally reflects: * Complex logic * Higher business risk * Extremely low test case counts may signal insufficient validation. #### Business & Operational Value * Ensures adequate QA coverage * Supports compliance and audit readiness * Helps QA leads plan testing effort *** ### User Story Stability #### Description Measures **how often a user story is modified after creation**, including changes to description, acceptance criteria, or scope.
#### Axis Details * **X-Axis:** User Story ID * **Y-Axis:** Stability Percentage (%) #### Interpretation * High stability = clear and well-defined requirements * Low stability = frequent changes, evolving business needs, or unclear expectations #### Business & Operational Value * Assesses requirement maturity * Encourages early stakeholder validation * Reduces rework and delivery delays *** ### Completion Date with Respect to Epic #### Description Tracks **completion trends over a time period**, such as by epic.
#### Axis Details * **X-Axis:** Time Period (Epic) * **Y-Axis:** Number of Items Completed #### Interpretation * Consistent completion trends indicate stable velocity. * Sudden drops highlight blockers or capacity issues. #### Business & Operational Value * Supports release forecasting * Helps identify long-term delivery patterns *** ### Story Points Completion #### Description Shows **story points assigned and completed**, reflecting effort and complexity.
#### Axis Details * **X-Axis:** Time Period / User Story * **Y-Axis:** Story Points #### Interpretation * Spikes indicate complex or high-effort stories. * Consistency reflects mature agile practices. #### Business & Operational Value * Measures team velocity * Improves capacity planning * Supports agile maturity assessment *** ### Status of Feature – New #### Description This widget displays the **status-wise distribution of newly created features**, providing visibility into how new features are progressing through their lifecycle.
#### Axis Details * **X-Axis:** Feature Name / Feature ID * **Y-Axis:** Count of Features #### Interpretation * Each bar represents the **number of features in a specific status**. * Higher values in **Proposed** indicate a strong backlog pipeline. * A balanced distribution between **In Progress** and **Released** reflects healthy execution flow. * Features remaining **In Progress** for extended periods may indicate dependencies or delivery bottlenecks. #### Business & Operational Value * Helps track feature readiness and delivery movement * Supports release and capacity planning * Identifies stagnation or prioritization gaps early *** ### Key Takeaways & Best Practices * Stable requirements reduce defects and rework * Frequent changes should trigger refinement sessions * Estimation accuracy improves with historical analysis * Combine defect, stability, and effort metrics for deeper insights # Release Dashboard Guide The **Release Management Dashboard** provides consolidated visibility into **release readiness, defect risk, execution quality, and sprint health** leading up to a release. It helps teams: * Assess release stability and risk * Track open and leaked defects * Monitor test execution coverage for releases * Analyze sprint-level quality and effort trends * Make informed go / no-go release decisions This dashboard is primarily used by **Release Managers, QA Leads, Product Owners, Delivery Managers, and Senior Stakeholders** during sprint reviews and release checkpoints. ### How to Use Dashboard Graphs (Common Instructions for All Widgets) Every widget on the dashboard includes a standard **three-dot (⋮) menu** in the top-right corner. These options behave the same across all graphs. * **Force Refresh:** Reloads the widget with the latest data. Always use this before reviews or release decisions. * **Enter Fullscreen:** Expands the graph for better visibility during meetings or presentations. * **Edit Chart:** Allows authorized users to modify filters, grouping, or metrics. * **Cross-Filtering Scoping:** Selecting data in one widget automatically filters related widgets for deeper analysis. * **View Query:** Displays the underlying logic or query used to generate the graph (mainly for admins/audits). * **View as Table:** Converts the graph into a table to view exact counts and records. * **Drill to Detail:** Opens individual defect records contributing to the graph. * **Share:** Generates shareable links or embedded views. * **Download:** Exports the graph or data as Image, PDF, or CSV/Excel. *** ### User Story Status in Sprint #### Description Displays the **status distribution of user stories** within a selected sprint.
#### Axis Details * **X-Axis:** User Story ID * **Y-Axis:** Number of User Stories #### Status Classification * Completed * Defined * Released * New #### Interpretation * A higher **Completed** count indicates strong sprint closure. * Many **New or Defined** stories late in the sprint may indicate scope creep. #### Business & Operational Value * Assesses sprint completion health * Helps determine sprint readiness for release * Highlights planning vs execution gaps *** ### Feature with Open Defect (Risk Analysis) #### Description Shows **features that currently have open defects**, highlighting release risk areas.
#### Axis Details * **X-Axis:** Feature Name / Feature ID * **Y-Axis:** Number of Open Defects #### Interpretation * Features with higher open defect counts represent **high-risk release components**. * Even a single critical defect can block a feature from release. #### Business & Operational Value * Supports risk-based release decisions * Helps prioritize defect closure * Identifies features needing additional validation *** ### Defect Leakage #### Description Displays **defects that escaped into later stages** (for example, production or UAT).
#### Axis Details * **X-Axis:** Project * **Y-Axis:** Defect Leakage Percentage (%) #### Interpretation * Higher leakage indicates gaps in test coverage or environment validation. * Zero or near-zero leakage reflects strong QA effectiveness. #### Business & Operational Value * Measures test effectiveness * Supports continuous improvement initiatives * Reduces production incidents *** ### User Story Defect State Wise #### Description Shows **defect distribution across user stories**, categorized by defect state.
#### Axis Details * **X-Axis:** User Story ID * **Y-Axis:** Number of Defects #### Interpretation * Stories with multiple open or reopened defects may require re-analysis. * Closed defects indicate stabilization. #### Business & Operational Value * Evaluates requirement quality * Identifies unstable user stories * Supports focused regression testing *** ### Test Case Executed for a Release – Platform Wise with Status #### Description Displays **test case execution results for a release**, grouped by platform.
#### Axis Details * **X-Axis:** Release / Platform (Web, Mobile, etc.) * **Y-Axis:** Count of Test Cases #### Status Classification * Passed * Failed * In Progress #### Interpretation * High pass percentage across platforms indicates release readiness. * Platform-specific failures highlight compatibility risks. #### Business & Operational Value * Ensures cross-platform coverage * Supports release certification * Reduces post-release issues *** ### Defect Status in a Sprint #### Description Shows **defect distribution by status** within a sprint.
#### Axis Details * **X-Axis:** Sprint * **Y-Axis:** Number of Defects #### Status Classification * Closed * Open * Duplicate #### Interpretation * A rising **Closed** trend shows stabilization. * High **Open** defects late in sprint indicate release risk. #### Business & Operational Value * Sprint quality assessment * Supports sprint exit decisions *** ### List of Test Cases in a Sprint – Platform Wise #### Description Displays a **tabular list of executed test cases**, grouped by sprint and platform.
#### Data Fields Explained * Sprint Name * Platform (Web / Mobile) * Test Case ID #### Interpretation Ensures visibility into platform-specific execution coverage. #### Business & Operational Value * Validates execution completeness * Supports audit and compliance needs *** ### Epic with Open Defect (Risk Analysis) #### Description Shows **epics that contain open defects**, indicating higher release risk.
#### Axis Details * **X-Axis:** Epic ID * **Y-Axis:** Number of Open Defects #### Interpretation * Epics with open defects should be carefully reviewed before release. #### Business & Operational Value * High-level risk analysis * Helps leadership make informed go / no-go decisions *** ### Test Case Executed for a Sprint – Platform Wise with Status #### Description Displays **test execution results for a sprint**, grouped by platform.
#### Axis Details * **X-Axis:** Sprint / Platform * **Y-Axis:** Count of Test Cases #### Interpretation * Balanced execution across platforms indicates good test planning. * Platform gaps may delay release sign-off. #### Business & Operational Value * Sprint execution completeness * Platform coverage validation *** ### Defect Created in a Sprint – Priority Wise #### Description Shows **defects created during a sprint**, categorized by priority.
#### Axis Details * **X-Axis:** Sprint * **Y-Axis:** Number of Defects #### Priority Classification * High * Medium * Low #### Interpretation * High-priority defect spikes signal quality risks. #### Business & Operational Value * Risk assessment * Sprint quality monitoring *** ### Defect Created in a Sprint – Severity Wise #### Description Displays **defect distribution by severity** for a sprint.
#### Axis Details * **X-Axis:** Sprint * **Y-Axis:** Number of Defects #### Severity Classification * Blocker * Critical * Major * Minor #### Interpretation * Blocker and Critical defects directly impact release readiness. #### Business & Operational Value * Release gating decisions * Quality trend analysis *** ### Defect Closed in a Sprint – Severity Wise #### Description Shows **defects closed in a sprint**, grouped by severity.
#### Axis Details * **X-Axis:** Sprint * **Y-Axis:** Number of Defects #### Interpretation * Closing high-severity defects improves release confidence. #### Business & Operational Value * Measures stabilization progress * Sprint closure validation *** ### Defect Closed in a Sprint – Priority Wise #### Description Displays **defects closed in a sprint**, categorized by priority.
#### Axis Details * **X-Axis:** Sprint * **Y-Axis:** Number of Defects #### Interpretation * Closing high-priority defects early reduces release risk. #### Business & Operational Value * Confirms defect triage effectiveness *** ### Task Elapse Time #### Description Tracks **time taken to complete tasks**.
#### Axis Details * **X-Axis:** Task ID / Time * **Y-Axis:** Elapsed Time #### Interpretation * Long elapse times highlight dependencies or inefficiencies. #### Business & Operational Value * Improves execution predictability * Supports process optimization *** ### Key Takeaways & Best Practices * Releases should not proceed with **open high-severity defects** * Always correlate **defect, execution, and story status** before sign-off * Use risk analysis widgets for **feature and epic-level decisions** * Monitor defect leakage to continuously improve QA effectiveness # Test Management Dashboard Guide The **Test Management Dashboard** provides complete visibility into **test case creation, ownership, coverage, execution readiness, and gaps** across projects, sprints, modules, and platforms. This dashboard helps teams: * Track test case creation trends * Measure test coverage at module, platform, and user story levels * Identify unexecuted or unused test cases * Analyze tester contribution and execution readiness * Improve overall test planning and test asset utilization It is primarily used by **QA Leads, Test Managers, Product Owners, and Delivery Managers** during test planning, sprint reviews, and quality audits. ### How to Use Dashboard Graphs (Common Instructions for All Widgets) Every widget on the dashboard includes a standard **three-dot (⋮) menu** in the top-right corner. These options behave the same across all graphs. * **Force Refresh:** Reloads the widget with the latest data. Always use this before reviews or release decisions. * **Enter Fullscreen:** Expands the graph for better visibility during meetings or presentations. * **Edit Chart:** Allows authorized users to modify filters, grouping, or metrics. * **Cross-Filtering Scoping:** Selecting data in one widget automatically filters related widgets for deeper analysis. * **View Query:** Displays the underlying logic or query used to generate the graph (mainly for admins/audits). * **View as Table:** Converts the graph into a table to view exact counts and records. * **Drill to Detail:** Opens individual defect records contributing to the graph. * **Share:** Generates shareable links or embedded views. * **Download:** Exports the graph or data as Image, PDF, or CSV/Excel. *** ### Count of Test Case – Module Wise #### Description Displays the **number of test cases created per module**.
#### Axis Details * **X-Axis:** Module Name * **Y-Axis:** Count of Test Cases #### Interpretation * Modules with higher test case counts usually represent **complex or high-risk areas**. * Modules with very few test cases may indicate **insufficient coverage**. #### Business & Operational Value * Helps ensure balanced test coverage * Identifies modules requiring additional test design * Supports risk-based testing strategies *** ### List of Test Executed – User Wise #### Description Shows **test execution contribution by each user**, categorized by execution type.
#### Axis Details * **X-Axis:** User Name * **Y-Axis:** Count of Test Executions #### Execution Type Classification * Manual * Automation * DDU (if applicable) #### Interpretation * Highlights individual tester contribution * Shows balance between manual and automated testing #### Business & Operational Value * Supports workload analysis * Helps identify automation adoption * Assists in performance reviews *** ### User-wise Count of Test Case Executions – Status Wise #### Description Displays **execution outcomes per user**, grouped by execution status.
#### Axis Details * **X-Axis:** User Name * **Y-Axis:** Count of Test Case Executions #### Status Classification * Passed * Failed #### Interpretation * High pass count indicates stable execution areas * High fail count may point to unstable builds or complex scenarios #### Business & Operational Value * Identifies execution risk areas * Supports capacity and ownership analysis *** ### Count of Test Case Creator – User Wise #### Description Shows **test case creation contribution by users**, segmented by platform.
#### Axis Details * **X-Axis:** User Name * **Y-Axis:** Count of Test Cases Created #### Platform Classification * Web * Android * iOS #### Interpretation * Highlights users contributing heavily to test design * Reveals platform-specific expertise #### Business & Operational Value * Encourages balanced test creation * Helps identify skill specialization *** ### List of Test Created in Month / Quarter – User Wise #### Description Provides a **tabular view of test cases created** in a specific time period by users.
#### Data Fields Explained * Project ID * Project Name * Test Case ID * Test Case Name #### Interpretation Helps track test creation velocity and timeline. #### Business & Operational Value * Supports audit and compliance needs * Measures test design throughput *** ### Count of Test Case – User Story Wise #### Description Displays **distribution of test cases mapped to user stories**.
#### Axis Details * **X-Axis:** User Story ID * **Y-Axis:** Count of Test Cases #### Interpretation * User stories with higher test counts are generally more complex * Stories with very few tests may be under-tested #### Business & Operational Value * Validates requirement-to-test coverage * Improves quality assurance at story level *** ### Count of Test Case – Platform Wise #### Description Shows **test case distribution across platforms**.
#### Axis Details * **X-Axis:** Platform (Web, Android, iOS, API, Database, Mobile, Functional) * **Y-Axis:** Count of Test Cases #### Interpretation * Ensures no platform is under-covered * Highlights testing focus areas #### Business & Operational Value * Supports cross-platform testing strategy * Helps align testing with product usage patterns *** ### Defect with Status for a Sprint – User Story Wise #### Description Displays **defects linked to user stories**, grouped by defect status for a sprint.
#### Axis Details * **X-Axis:** User Story ID * **Y-Axis:** Count of Defects #### Interpretation * High defect counts against a story indicate requirement or design gaps * Closed defects indicate stabilization #### Business & Operational Value * Evaluates story quality * Supports root cause analysis *** ### List of Test Created – User Wise (Up) #### Description Shows **test cases created by users**, categorized by creation type.
#### Axis Details * **X-Axis:** User Name * **Y-Axis:** Count of Test Cases Created #### Creation Type * Manual * Automation * DDU #### Interpretation Highlights individual contribution to test assets. #### Business & Operational Value * Encourages ownership in test design * Supports automation planning *** ### Test Case Execution Status for a Sprint – User Story Wise #### Description Displays **execution status of test cases mapped to user stories** for a sprint.
#### Axis Details * **X-Axis:** User Story ID * **Y-Axis:** Number of Test Cases #### Interpretation * Shows execution completeness at story level * Identifies untested or partially tested stories #### Business & Operational Value * Improves sprint exit quality * Ensures no story moves forward untested *** ### Count of Test Case That Are Never Executed for a Project #### Description Displays **test cases that have never been executed**, grouped by project.
#### Axis Details * **X-Axis:** Project Name * **Y-Axis:** Count of Never Executed Test Cases #### Interpretation * High values indicate unused or obsolete test cases * Suggests need for test suite cleanup #### Business & Operational Value * Optimizes test repository * Reduces maintenance overhead * Improves execution efficiency *** ### Key Takeaways & Best Practices * Ensure **every user story has adequate test coverage** * Regularly review **never-executed test cases** to remove redundancy * Balance test creation across **modules and platforms** * Encourage automation for stable and repetitive scenarios * Use test management insights alongside **Execution, Defect, and Release dashboards** for full quality visibility # Test Execution Dashboard Guide The **Test Execution & Production Monitoring Dashboard** provides end-to-end visibility into **test execution progress, execution quality, defect trends, execution coverage, and environment readiness**. This dashboard enables stakeholders to: * Monitor execution health in real time * Track pass/fail trends across users and projects * Identify execution gaps and unexecuted test cases * Correlate execution results with defect trends * Ensure infrastructure and device readiness It is primarily used by **QA Leads, Test Managers, Delivery Managers, and Release Teams** during execution cycles and production monitoring. ### How to Use Dashboard Graphs (Common Instructions for All Widgets) Every widget on the dashboard includes a standard **three-dot (⋮) menu** in the top-right corner. These options behave the same across all graphs. * **Force Refresh:** Reloads the widget with the latest data. Always use this before reviews or release decisions. * **Enter Fullscreen:** Expands the graph for better visibility during meetings or presentations. * **Edit Chart:** Allows authorized users to modify filters, grouping, or metrics. * **Cross-Filtering Scoping:** Selecting data in one widget automatically filters related widgets for deeper analysis. * **View Query:** Displays the underlying logic or query used to generate the graph (mainly for admins/audits). * **View as Table:** Converts the graph into a table to view exact counts and records. * **Drill to Detail:** Opens individual defect records contributing to the graph. * **Share:** Generates shareable links or embedded views. * **Download:** Exports the graph or data as Image, PDF, or CSV/Excel. *** ### User-wise Count of Test Case Executions – Status Wise #### Description This widget displays the **number of test cases executed by each user**, categorized by execution status.
#### Axis Details * **X-Axis:** User Name / User ID * **Y-Axis:** Count of Test Case Executions #### Status Classification * Passed * Failed * Aborted / Not Executed (if applicable) #### Interpretation Each bar represents a user, segmented by execution status. A higher **Passed** count indicates effective execution, while a higher **Failed** count may point to unstable builds or complex test scenarios. #### Business & Operational Value * Assesses tester productivity * Highlights execution ownership * Helps balance workload *** ### Count of Defects Logged in Execution Plan – Execution Date Wise #### Description Shows the **number of defects logged during test execution**, grouped by execution date.
#### Axis Details * **X-Axis:** Execution Date * **Y-Axis:** Count of Defects Logged #### Interpretation Spikes indicate unstable builds or high-risk execution windows, while downward trends suggest improved quality. #### Business & Operational Value * Correlates failures with defect trends * Identifies problematic builds early * Supports release quality assessment *** ### List of Registered Devices in a Project #### Description Displays a **tabular list of devices registered** under each project.
#### Data Fields Explained * Project ID * Project Name * Technology Type (Android, iOS, Web, etc.) * Device Name / Device Identifier #### Interpretation Provides visibility into device availability for execution. #### Business & Operational Value * Ensures device coverage * Prevents execution delays due to missing infrastructure * Supports cross-platform testing *** ### List of Registered Machines – Client Wise #### Description Displays a **client-wise list of machines** available for test execution.
#### Data Fields Explained * Client Name * Machine Name * OS / Platform Details #### Interpretation Shows infrastructure readiness across clients. #### Business & Operational Value * Supports distributed execution * Ensures environment readiness * Helps with infrastructure planning *** ### Project-wise Count of Test Case Executions – Status Wise #### Description Displays **execution status distribution across projects**.
#### Axis Details * **X-Axis:** Project Name * **Y-Axis:** Count of Test Case Executions #### Interpretation High **Passed** counts indicate stable projects, while high **Failed** counts highlight project-level risk areas. #### Business & Operational Value * Enables project health comparison * Helps prioritize stabilization efforts *** ### Overall Execution Plan Status #### Description Provides a **high-level summary of the execution plan status**.
#### Status Categories * Passed * Failed * Not Executed * Inprogress * Blocked #### Interpretation A large **Not Executed** portion indicates incomplete execution and potential delivery risk. #### Business & Operational Value * Quick execution health snapshot * Useful for management and release reviews *** ### Key Takeaways & Best Practices * Monitor **Not Executed** trends daily to avoid last-minute risks * Correlate execution failures with defect trends for root cause analysis * Ensure device and machine readiness before execution cycles * Use user-wise reports for capacity planning and balancing * Combine execution insights with **Defect and Requirement dashboards** for complete visibility # Defect Dashboard Guide Welcome to the **Defect Management Dashboard – Widgets & Reports Help Guide**. This document explains how to **read, interpret, and use** each dashboard widget effectively. It is designed for **clients, business stakeholders, QA teams, developers, product owners, and management** to ensure consistent understanding of quality metrics and reporting. The dashboard converts raw defect data into actionable insights that help assess **release readiness, product stability, team performance, and production risk**. ### How to Use Dashboard Graphs (Common Instructions for All Widgets) Every widget on the dashboard includes a standard **three-dot (⋮) menu** in the top-right corner. These options behave the same across all graphs. * **Force Refresh:** Reloads the widget with the latest data. Always use this before reviews or release decisions. * **Enter Fullscreen:** Expands the graph for better visibility during meetings or presentations. * **Edit Chart:** Allows authorized users to modify filters, grouping, or metrics. * **Cross-Filtering Scoping:** Selecting data in one widget automatically filters related widgets for deeper analysis. * **View Query:** Displays the underlying logic or query used to generate the graph (mainly for admins/audits). * **View as Table:** Converts the graph into a table to view exact counts and records. * **Drill to Detail:** Opens individual defect records contributing to the graph. * **Share:** Generates shareable links or embedded views. * **Download:** Exports the graph or data as Image, PDF, or CSV/Excel. ### Defect Status * **New:** Defect logged and awaiting review. * **Open:** Defect accepted and ready to be worked on. * **In Progress:** Defect actively being fixed. * **Fixed / Resolved:** Fix completed and pending QA verification. * **Retest:** Defect ready for validation. * **Closed:** Fix verified and completed. * **Reopened:** Issue persists after closure. * **Rejected:** Invalid or duplicate defect. * **Deferred:** Fix postponed to a future release. *** ### Quality & Stability Metrics These widgets help determine **overall product health and release readiness**. #### 1. Defect by Severity for Sprint of Release **Purpose**\ This widget helps evaluate the **technical risk and stability** of each sprint or release by classifying defects based on their impact on the system. It is one of the most critical graphs for **release readiness decisions**.
**Axis Breakdown** * **X-Axis (Horizontal):** Sprint or Release identifiers (e.g., SP-1, SP-130, SP-152). Each bar represents one sprint. * **Y-Axis (Vertical):** Total number of defects logged in that sprint. **How to Read the Graph** * Each sprint is represented by a vertical bar. * The bar is divided into color-coded segments, each representing a severity level (Minor, Major, Blocker, Critical). * The total height of the bar equals the total number of defects in that sprint. **How to Interpret** * **Blocker/Critical present:** Sprint is unstable and not suitable for release. * **Major-dominated bars:** Core functionality issues exist. * **Minor-heavy bars:** Indicates polish and usability issues rather than functional risk. * **Trend analysis:** Decreasing bar height across sprints shows improving quality maturity. **Business & QA Actions** * Stop release if Blocker/Critical defects exist. * Prioritize root cause analysis for sprints with repeated high Major defects. #### 2. Defect by Priority for Sprint of a Release **Purpose**\ This widget represents defects categorized by **business urgency**, helping teams understand what must be fixed immediately versus what can be deferred.
**Axis Breakdown** * **X-Axis:** Sprint identifiers. * **Y-Axis:** Number of defects. **How to Read the Graph** * Each bar represents a sprint. * Color segments represent priority levels (High, Medium, Low). **How to Interpret** * **High-priority-heavy bars:** Immediate business risk. * **Consistent High priority across sprints:** Indicates planning or requirement clarity issues. * **Medium/Low dominance:** Indicates manageable backlog. **Business & QA Actions** * High priority defects must be resolved before sprint sign-off. * Review prioritization rules if High-priority backlog persists. #### 3. Defect by State for Sprint of a Release **Purpose**\ This widget tracks how efficiently defects move through their lifecycle within and across sprints.
**Axis Breakdown** * **X-Axis:** Sprint identifiers. * **Y-Axis:** Defect count. **How to Read the Graph** * Each bar is segmented by defect state (New, In Progress, Fixed, Closed, etc.). * Distribution shows where defects are currently stuck. **How to Interpret** * **High Closed:** Healthy sprint completion. * **High New late in sprint:** Late discovery risk. * **High In Progress:** Development bottlenecks. **Business & QA Actions** * Use this graph in daily standups to unblock work. #### 4. Defect Distribution (Pie Chart) **Purpose**\ Provides a high-level snapshot of the **overall defect backlog health** at any point in time.
**How to Read the Graph** * Each slice represents a defect status. * Slice size corresponds to percentage of total defects. **How to Interpret** * **Closed dominant:** Stable product. * **New/Open dominant:** Growing backlog and risk. * **Reopened visible:** Fix quality issues. **Business & QA Actions** * Use during leadership reviews for quick decision-making. *** ## Team Performance & Workload These widgets ensure **balanced workload and efficient delivery**. #### 5. Defect Removal Efficiency (DRE) **Purpose**\ Measures how effectively defects are caught **before production**.
**Axis Breakdown** * **X-Axis:** Project names * **Y-Axis:** Efficiency score (0–1) **How to Read the Graph** * Taller bars = better defect prevention **How to Interpret** * Near 1.0 → Strong QA process * Below 0.6 → High production leakage **Business & QA Actions** * Strengthen regression & automation for low DRE projects #### 6. Defect Assigned User Wise with Status **Purpose**\ Visualizes **workload distribution** across team members.
**Axis Breakdown** * **X-Axis:** User names * **Y-Axis:** Assigned defect count **How to Read the Graph** * Taller bars = higher workload **How to Interpret** * Uneven bars → Burnout or bottlenecks * High In Progress → Skill dependency **Business & QA Actions** * Redistribute work * Enable cross-training #### 7. Defect Logged Based on Created By **Purpose**\ Shows **who is discovering defects**.
**Axis Breakdown** * **X-Axis:** Creator name * **Y-Axis:** Defect count **How to Read the Graph** * Taller bars = higher contribution **How to Interpret** * High QA → Strong testing * Developer entries → Shift-left quality **Business & QA Actions** * Encourage dev-side validation * Recognize top contributors *** ## Functional & Technical Analysis These graphs identify **application weak spots**. #### 8. Defect Logged Module Wise **Purpose**\ Identifies **modules with high defect density**.
**Axis Breakdown** * **X-Axis:** Module names * **Y-Axis:** Defect count **How to Interpret** * Tall bars → Technical hotspots **Business & QA Actions** * Increase regression coverage * Consider refactoring #### 9. Defect in a Sprint Grouped by Category **Purpose**\ Classifies defects by **technical type** (UI, DB, Logic).
**Axis Breakdown** * **X-Axis:** Categories * **Y-Axis:** Defect count **How to Interpret** * UI-heavy → Need UI automation * Logic-heavy → Code/design issues **Business & QA Actions** * Adjust testing strategy accordingly #### 10. Defect in a Sprint Grouped by Labels **Purpose**\ Tracks defects using **custom tags**.
**How to Interpret** * Useful for audits, hotfix tracking, regression cycles **Business & QA Actions** * Use labels consistently for reporting accuracy #### 11. Feature Defect State Wise **Purpose**\ Measures defect health at the **feature level**.
**Axis Breakdown** * **X-Axis:** Feature names * **Y-Axis:** Defect count **How to Interpret** * High open defects → Feature instability **Business & QA Actions** * Delay feature enablement #### 12. Epic Defect State Wise **Purpose**\ Provides a **strategic quality view** by Epic.
**Axis Breakdown** * **X-Axis:** Epic codes * **Y-Axis:** Defect count **How to Interpret** * High defects → Roadmap risk **Business & QA Actions** * Use in release planning *** ## Requirements & User Stories Captures and documents what the system must do from the user’s perspective to guide development. #### 13. User Story Defect State Wise (Chart) **Purpose**\ Identifies **high-risk user stories**.
**Axis Breakdown** * **X-Axis:** User Story IDs * **Y-Axis:** Defect count **How to Interpret** * High counts → Design or acceptance gaps **Business & QA Actions** * Review acceptance criteria #### 14. Defect with Status for a Sprint – User Story Wise (Table) **Purpose**\ Provides **detailed defect-to-story mapping**.
**How to Interpret** * Analyze patterns during retrospectives **Business & QA Actions** * Improve story refinement *** ## Execution & Production Monitoring Tracks system performance and operations to ensure smooth execution and timely issue detection. #### 15. Defect with State, Priority and Severity (Detailed Grid) **Purpose**\ Acts as the **master defect list** for daily triage.
**How to Interpret** * Review row-by-row for execution decisions **Business & QA Actions** * Use in daily triage meetings #### 16. Test Execution Status Overview **Purpose**\ Tracks **testing progress**, independent of defects.
**How to Interpret** * High Not Executed → Schedule risk * High Failed → Product instability **Business & QA Actions** * Re-plan testing timelines #### 17. Production Defect Logged – Client Wise **Purpose**\ Tracks **escaped defects** reported by clients.
**Axis Breakdown** * **X-Axis:** Client names * **Y-Axis:** Defect count **How to Interpret** * Any value > 0 = Quality escape **Business & QA Actions** * Immediate RCA and prevention *** ### Final Takeaway This dashboard is a **decision-support system**, not just a report.\ When interpreted correctly, it enables **faster releases, higher quality, and stronger client trust**. # Release & Sprints In Agile software development, Releases and Sprints play a crucial role in delivering high-quality software in an iterative and structured manner. SimplifyQA provides built-in Release and Sprint Management features to help teams plan, track, and execute their development and testing activities efficiently. ### What is a Release? A Release is a planned delivery of a set of features or fixes within a specific timeframe. It consists of multiple Sprints, each contributing towards the final product. Releases help teams: * Plan and organize feature deliveries based on business priorities. * Track progress across multiple sprints for better visibility. * Ensure that all features are tested and validated before deployment. ### What is a Sprint? A Sprint is a short, time-boxed iteration (typically 1-4 weeks) where teams focus on developing and testing a defined set of user stories. Each Sprint contributes towards achieving the overall Release goal. Sprint Management in SimplifyQA allows teams to: * Define and prioritize backlogs for each Sprint. * Assign tasks to developers, testers, and stakeholders. * Track progress using burndown charts and status reports. * Conduct automated and manual testing within the Sprint cycle. By integrating Release and Sprint Management, SimplifyQA ensures that Agile teams can deliver faster, track progress seamlessly, and maintain high-quality software releases. # Introduction to Releases ### What is a Release? In SimplifyQA, a Release represents a planned deployment of software that includes a set of features, enhancements, and bug fixes. Releases help teams manage the software development lifecycle efficiently by tracking progress, organising work, and ensuring timely delivery. **Key Features of Releases in SimplifyQA** * Plan and Track: Organise features and user stories into releases for better tracking. * Traceability: Link requirements, test cases, and defects to a release for end-to-end visibility. * Sprint Integration: Associate releases with sprints to align with Agile methodologies. **Accessing the Releases Module** * From the User Navigation Panel, go to Release Management ▶ Releases.
* The Releases page will open, displaying a list of existing releases with details like status, associated sprints, and version numbers.
# Create & Manage Release & Sprint This document provides instructions on how to create a new release and sprint in SimplifyQA. ### Creating a New Release 1. **Access the Release Creation Page:** * Navigate to the Releases section from the left menu. * Click the "Create" button. * Select 'Release' option from the dropdown.
2. **Enter Release Details:** * **Name:** Provide a clear and concise name for the release. * **Owner:** Select the project owner responsible for the release. * **Projects:** Select the project(s) you want to assign the Epic to. When you click on the Project field, a dropdown will display all the projects you have access to. You can either select a single project or multiple projects, depending on your requirements. * **Planned Start Date:** Set the planned start date for the release. * **Planned End Date:** Set the planned end date for the release. * **Estimated Effort:** Estimate the total effort required for the release (in hours or story points). * **Description:** Provide a brief description of the release's goals and objectives.
3. **Save the Release:** * Click the "Create" button to save the new release. * Click the 'Save & Create Sprint' to save the new release and create sprint. ### Creating a New Sprint 1. **Sprint Creation Page:** * Navigate to the Sprints section from the left menu. * Click the "Create Sprint" button. 2. **Enter Sprint Details:** * **Name:** Provide a clear and concise name for the sprint. * **Owner:** Select the project owner responsible for the sprint. * **Start Date:** Set the start date for the sprint. * **End Date:** Set the end date for the sprint. * **Release:** Select the release to which the sprint belongs. * **Description:** Provide a brief description of the sprint's goals and objectives.
3. **Save the Sprint:** * Click the "Create" button to save the new sprint. ### Plan your Sprint Once a release and sprint have been created, start planning the work for your team. #### To add stories, tasks and defects to your sprint: * Navigate to sprint plan. * Drag and drop the items in the designated sprint {% hint style="info" %} Note: Create and plan sprints for the future to align with the product roadmap. {% endhint %} ### Start the Sprint * **Navigate to the Sprint:** Open the specific sprint you want to start. * [**Start the Sprint**](/release-and-sprints/start-and-close-a-sprint)**:** Click on the "Start Sprint" button. This action officially initiates the sprint. * **Check Sprint Details:** Verify the sprint details and the tasks, defects or user stories assigned to it. * **Confirm:** Click on 'Confirm' to start the sprint. ### Sprint states in SimplifyQA You come across 2 different sprint states in SimplifyQA: 1. New 2. In-progress 3. Completed * **New:** A newly created sprint that has not yet begun and means that * No work has started. * The sprint backlog is being defined or refined. * The team is preparing for the sprint planning meeting. * **What are the next steps to start the sprint?** * Define the sprint goal. * Select backlog items to be included in the sprint. * Break down tasks and estimate effort. * Assign tasks to team members. * **In-Progress:** A sprint that is currently underway & active and means that * The sprint planning meeting has been completed. * The team is actively working on tasks and user stories. * Daily stand-ups are conducted to track progress and address issues. * Regular reviews and retrospectives are scheduled. * **What actions need to be taken to ensure the sprint is goal is achieved?** * Daily stand-ups to track progress and address impediments. * Work on assigned tasks and user stories. * Collaborate with team members to resolve issues. * Conduct regular code reviews and testing. * **Completed:** A sprint that has been finished and all its tasks have been completed and means that * The sprint review and retrospective meetings have been conducted. * The team has delivered the planned work. * The sprint backlog has been updated to reflect the completed work. * The team is ready to start the next sprint. * **Before closing the sprint, you need to ensure,** * Conduct a sprint review to demonstrate completed work. * Hold a retrospective meeting to identify lessons learned and areas for improvement. * Update the product backlog with completed and remaining items. * Prepare for the next sprint planning meeting. ### Close the Sprint * **Navigate to the Sprint:** Open the specific sprint you want to close. * **Close the Sprint:** Click on the "Close Sprint" button. This action officially close the sprint. * **Verify Sprint Completion:** Ensure all tasks and user stories within the sprint are marked as "completed." Review the sprint backlog to confirm that all planned work has been finished. * **Confirm:** Click on 'Confirm' to close the sprint. {% hint style="info" %} **Additional Tips** * **Break Down Work into Tasks:** Within each sprint, create tasks to break down the work into smaller, manageable chunks. * **Estimate Task Effort:** Assign estimated effort (in hours or story points) to each task which gives you visibility on the capacity of the team. * **Assign Tasks to Team Members:** Assign tasks to the appropriate team members, ensure to tag multiple teams if there are stories which requires cross functional team to be involved. * **Track Sprint Progress:** Monitor the progress of each sprint and make adjustments as needed. * **Review and Reflect:** After each sprint, conduct a retrospective meeting to review what went well, what didn't, and what can be improved in future sprints. {% endhint %} # Start & Close a Sprint In Agile project management, starting and closing a sprint are essential to ensure structured development, clear objectives, and continuous improvement. **Start Sprint -** Starting a sprint allows teams to define goals, plan work, and allocate tasks. It ensures alignment between stakeholders and developers on the sprint scope, expected deliverables, and priorities. **Close Sprint -** Closing a sprint helps assess completed work, identify blockers, and gather feedback. It includes sprint review and retrospective meetings, enabling teams to improve processes and enhance productivity for future sprints. **Viewing Sprints Under a Release** To view all sprints associated with a release: 1. Click the accordion icon next to the release.
2. All associated sprints will be displayed.
#### Starting a Sprint 1. Click the "View Details" icon next to a sprint to modify details.
2. Click "Start Sprint" on the sprint details page.
3. Confirm the action. {% hint style="info" %} ***Note**: Starting a sprint will also start its associated release. The release will automatically stop once all its sprints are closed.* {% endhint %} #### Closing a Sprint To close a sprint: 1. Open the sprint details by clicking "View Details". 2. Click "Close Sprint" and confirm the action.
### Using the Release Plan Module You can also start a sprint from the Release Plan Module, which provides a visual representation of the release and sprint using a Gantt Chart. #### Navigating to Release Plan To manage sprints, navigate through the User Navigation Panel: 1. Click on Release Management. 2. Select Release Plan.
* Hovering over the sprints displays details like: * Status (New, In Progress, Completed) – indicated by color. * Assigned Dates.
* Click the "View Details" icon to open full sprint details, where you can start or close the sprint.
* You can also start the sprint by clicking the green start icon.
# Start & Close a Release # Create and Manage your Requirements In SimplifyQA, requirements are fundamental elements of the software testing process. They define the features, specifications, and expectations that need to be tested and validated. Managing requirements effectively ensures that the testing team can track, prioritize, and address them in an organized manner, resulting in a more efficient and effective testing cycle. ### What are Requirements? Requirements are clear, detailed descriptions of what a system, feature, or functionality must do. They serve as a foundation for creating test cases, guiding development efforts, and ensuring that the final product meets stakeholder expectations. In SimplifyQA, you can create, manage, and track these requirements throughout the software development lifecycle. They act as a reference point for your testing efforts, helping to ensure all aspects of a project are covered. ### Why is Managing Requirements Important? Effective requirement management is crucial for several reasons: * **Clear Communication:** Properly defined requirements prevent misunderstandings between teams (development, QA) and ensure everyone is aligned on the project goals. * **Traceability:** You can trace every requirement from creation through development to testing, ensuring that no requirement is overlooked or ignored. * **Prioritisation:** Not all requirements are equally important. By managing requirements, you can prioritise them based on critical business needs and ensure that high-priority items are addressed first. * **Efficiency:** A well-managed set of requirements helps the team work more efficiently by streamlining testing, reducing rework, and focusing on the most relevant tasks. ### Key Features of Managing Requirements in SimplifyQA **1. Organizing Requirements** SimplifyQA provides robust features for organising your requirements, making it easier to manage large projects with multiple features and specifications. You can categorise requirements based on various attributes such as: * **Type:** Epic, Feature, User Stories, etc. * **Priority:** High, Medium, Low * **Status:** New, In Progress, Completed These categories allow you to filter and view requirements based on what’s most relevant at any given time. **2. Linking Requirements to Test Cases** One of the most powerful features of SimplifyQA is the ability to link requirements directly to test cases. This ensures that each requirement has a corresponding test case that verifies its implementation. This traceability ensures complete test coverage and helps identify gaps in the testing process. **3. Collaboration and Communication** Managing requirements in SimplifyQA isn't just about tracking them; it's about collaborating across teams. Stakeholders, developers, and testers can add comments, notes, and attachments to each requirement. This promotes active communication and ensures that all relevant information is captured in one place, making it easier to make informed decisions. **4. Reporting and Analytics** SimplifyQA offers advanced reporting and analytics features that provide insight into the status and health of your requirements. You can generate reports that show the overall progress of requirements, identify delayed items, and analyse bottlenecks. These reports help project managers and stakeholders make data-driven decisions to ensure that the project stays on track. Effectively creating and managing your requirements in SimplifyQA is essential to maintaining project clarity and ensuring successful testing outcomes. By using SimplifyQA's features, you can streamline your process, keep all team members aligned, and ensure that each requirement is thoroughly tested and implemented. # Introduction to Requirement Management The Requirement Management module in SimplifyQA allows you to seamlessly track and manage your Epics, Features, and User Stories within a single interface. This module is designed to streamline your workflow and ensure that all requirements are properly documented, tracked, and aligned with project goals. Key Components of Requirement Management are - * **Epics** * High-level initiatives that encompass a large body of work. * Acts as the foundation for Features and User Stories. * **Features** * Functionalities that contribute to achieving an Epic. * Provide detailed objectives that can be broken down further into User Stories. * **User Stories** * Simple descriptions of a feature told from the perspective of the user. * Focus on delivering specific value to the user. Each of these components can be managed effectively within the Requirement Management module to ensure project alignment and traceability. # Create & Manage Epic The Requirement Management module in SimplifyQA allows you to create, manage, and track your Epics, Features, and User Stories. ### Prerequisites To create and delete Epic in the Requirement Management module, the user must be granted the appropriate [privileges by the admin](/admin-controls-and-configurations/manage-projects-and-users/project-settings/manage-roles-and-privileges). These permissions are required to perform these actions. Follow the steps below to create and manage Epics effectively. ### Navigating to the Requirement Management Module * From the User Navigation Panel, click on the Requirement Management module. * This will open the Requirement Management page, where you can create and manage your Epics, Features, and User Stories.
### Creating an Epic 1. **Open the Create Dropdown** 1. On the Requirement Management page, click on the "+ Create" button. 2. Select "Create Epic" to proceed.
2. **Fill out the Epic details** 1. A form will open to create your Epic. Fill out the mandatory fields, including: 1. Name 2. **Project:** Select the project(s) you want to assign the Epic to. When you click on the Project field, a dropdown will display all the projects you have access to. You can either select a single project or multiple projects, depending on your requirements. This means that an Epic can be shared and accessed across multiple projects if needed, ensuring better collaboration and visibility across teams.
**iii. Status:** Set the status of the Epic. These statuses can be configured in the **Admin** panel to align with project requirements.
1. Planned Start Date and Planned End Date 2. **Estimated Effort:** Specify the effort required for the Epic, which can be measured in either story points or hours. * The value of a story point can be determined by the users and configured in the [Admin settings](/admin-controls-and-configurations/manage-projects-and-users/project-settings).
For better traceability and mapping, it is recommended to fill out all fields, including: * **Attachments**: Upload relevant files or documents. * **Linkages**: Add references or connections to other items in the tool. * **Assigned User:** Assign the Epic to a team member or a owner. * **Actual Effort:** Enter the actual effort spent on the Epic. This field helps track the time or resources utilised during execution, providing a comparison against the estimated effort. * **Labels:** Add labels or tags to categorise and organise the Epic. Labels make it easier to filter and search for Epics based on specific criteria. * **Team:** Assign a team or group responsible for working on the Epic. This ensures clarity on ownership and collaboration within the project.
3. After filling out the details, click "Save" to save the Epic. ### Viewing and Updating Epics #### Locating the Epic 1. Once saved, the Epic will appear on the Requirement Management Page. 1. It will also be visible in the Tree Panel on the left side when set to User Story View.
**Editing an Epic** 1. To view or update an Epic, you can either click on "View Details" arrow for the desired Epic or you can right click the desired epic from the **tree view** in which you will have the option to edit. 2. This will open the Epic form, where you can make any required changes, such as: * Updating fields * Changing attachments * Modifying status
3. Save the changes to update the Epic. #### **Inline Editing in Table View** You can now make **quick edits directly in the table**—no need to open the Epic form. To edit an Epic in the table: * Simply **click on the field** you want to update (e.g., **Name**, **Owner**, **State**, **Planned Start Date**, **Planned End Date**). * The field will become **editable**, allowing you to **type in or select** the updated value right there. * Once done, click outside the field to save the change. ​​
This **inline editing** feature significantly improves efficiency when making multiple changes or managing large sets of Epics at once. This streamlines Epic management by saving time and clicks, especially useful for high-volume projects. #### Deleting and Epic 1\. To delete an Epic, select the checkbox next to the desired Epic, and the delete icon will appear next to the "+Create" button. Alternatively, you can right-click on the Epic in the tree view and select "Delete" from the menu. 2\. Confirm the action to permanently remove the Epic. # Create & Manage Features In the Requirement Management module of SimplifyQA, you can also create and manage Features, which are subsets of Epics. The entire market value of an Epic is broken down into different features, each forming an independent deliverable unit. ### Prerequisites To create and delete features in the Requirement Management module, the user must be granted the appropriate privileges by the admin. These permissions are required to perform these actions. ### Creating a Feature 1. From the User Navigation Panel, go to the Requirement Management Module.
2. Click the “+ Create” button located at the top of the Requirement Management page. 3. In the dropdown menu, select "Create Feature".
4. A form will open to input the details of the Feature. Fill out the following fields: 1. **Name:** Enter a meaningful name for the Feature. 2. **Planned Start Date and Planned End Date:** Specify the timeline for delivering the Feature. 3. **Estimated Effort:** Input the estimated effort required to complete the Feature. This can be measured in either Story Points or Hours.\ The value of Story Points can be defined in the [Admin settings](/admin-controls-and-configurations). 4. **Priority:** Assign a priority level to the Feature (e.g., High, Medium, Low). 5. **Project:** Select the project you want to assign the Feature to.
Additional optional fields: * **Epic:** Select the parent Epic under which this Feature will be grouped. * **Description:** Provide additional details or context for the Feature. * **Assigned User:** Assign the Feature to a team member for accountability. * **Labels:** Add tags to categorize or organize the Feature for easier filtering. * **Status:** Set the status of the Feature (e.g., New, In Progress, Completed). * **Team:** Specify the team responsible for implementing the Feature. * **Attachments:** Upload any relevant documents or files related to the Feature. * **Linkages:** Create references to other items (e.g., test cases, defects) in SimplifyQA.
5. Once all details are filled in, click “Save”. \ The Feature will now appear under the selected Epic on the Requirement Management page and in the Tree Panel on the left.
### Managing Features You can view, update, or delete Features as needed. **Viewing and Updating a Feature** 1. Locate the Feature in the Requirement Management module under the associated Epic. 2. Click on “View Details” next to the Feature you want to edit.
3. Update any fields as required, such as effort, assigned user, or status. 4. Save the changes by clicking “Save”. #### Deleting a Feature 1. Select the feature you want to delete by clicking on the check box next to the desired feature and the delete icon will show up 2. Confirm the action to permanently remove the Feature. ### **Actions in the Tree View for Features** In addition to managing Features from their detail pages, several quick actions can be performed directly within the Tree View by right-clicking on the Feature. These actions include: * **Edit** – Quickly view and update the Feature without leaving the Tree view. * **Add User Story** – Create and associate a new User Story directly under the selected Feature. * **Copy Link** – Instantly copy a direct link to the Feature for easy sharing. * **Delete** – Remove the Feature directly from the Tree view, streamlining project management and organization.
Features can also be created directly from the Tree view. Simply right-click on the desired Epic, and you'll see the "Add Feature" option, which will redirect you to the Feature creation page.
# Create & Manage User Stories The Requirement Management module in simplifyQA allows users to create, manage, and track User Stories. A User Story is a short description of a functionality or requirement written from the perspective of the end user. In simplifyQA, User Stories are connected to Epics and Features, helping teams break down large features into manageable pieces. ### Prerequisites To create and delete User Story in the Requirement Management module, the user must be granted the appropriate [privileges by the admin.](/admin-controls-and-configurations/manage-projects-and-users/project-settings/manage-roles-and-privileges) ### Creating a User Story 1. **Add a new User Story** 1. From the User Navigation Panel, go to the Requirement Management Module.
b. Click on the '+ Create' button at the top of the Requirement Management page. c. In the dropdown menu, select 'Create User Story'.
d. A form will open for you to fill out the User Story details. 2. **Fill out the User Story details** * **Name:** Provide a descriptive title for the User Story. * **Assignee**: Assign the User Story to a team member. * **Acceptance Criteria**: Define clear acceptance criteria to specify when the User Story will be considered complete. * **Estimated Effort:** Specify the effort required to complete the User Story in either story points or hours.
For better traceability and organisation, it is recommended to fill out the following fields: * **Epic**: Link the User Story to a relevant Epic. * **Feature**: Select the associated Feature, if applicable. * **Release**: Specify the Release in which the User Story is planned. * **Sprint**: Assign the User Story to a Sprint for tracking progress. If a **User Story** is not assigned to a **Release** or **Sprint**, it is considered part of the **Backlog**. These backlog items remain available in the **Sprint/Release Planning Board** for future planning and assignment. * **Type**: Choose the type of User Story—either Gherkin or Normal. * **Module**: **Module** in SimplifyQA is a top-level hierarchy within a project, serving as a common element across various application artefacts. It plays a crucial role in organising and managing test cases, requirements, and defects efficiently. * **Associated User Story**: An **Associated User Story** refers to a user story that is **linked or related** to another user story due to dependencies, shared functionality, or relevance within the same feature or module. * **Impacted User Story**: An **Impacted User Story** refers to a user story that is **affected by changes** made to another user story. * **Deployment Status**: Track the deployment status of the User Story. * **Attachments**: Upload relevant files or documents. * **Linkages**: Add references or connections to other items in the tool.
4. After filling in all the details, click 'Save'. ### Managing User Stories Viewing and editing a User Story 1. Navigate to the Tree Panel on the left to locate the User Story under its parent Epic or Feature.
2. Click on 'View Details' next to the User Story to open its details page.
3. Update any of the fields as required, such as effort, assigned user, or priority. 4. Click 'Save' to save the changes. ### Deleting a User Story: 1. Select the User story you want to delete by clicking on the check box next to the desired User Story and the delete icon will show up next to '+ Create'. 2. Confirm the action to permanently remove the User Story. ### Actions in the Tree View In addition to managing User Stories from their detail pages, several quick actions can be performed directly within the **Tree View** by **right-clicking on the User Story**. These include: 1. **Edit** – Quickly view and update the User Story without navigating away. 2. **Add Task** – Create and associate tasks directly under the selected User Story. 3. **Copy Link** – Instantly copy a direct link to the User Story for easy sharing. 4. **Delete** – Remove the User Story directly from the Tree View, streamlining cleanup and backlog management.
User Stories can also be created directly from the Tree view. Simply right-click on a Feature and epic, and you'll see the "Add User Story" option, which will redirect you to the User Story creation page.
# Plan and track your stories User stories are essential for defining software functionality from an end-user perspective. In SimplifyQA, you can efficiently plan, organise, and track user stories throughout the software development lifecycle. This ensures clear communication, structured execution, and comprehensive testing. ### Why Plan and Track User Stories? * **Align Development & Testing:** Ensure that test cases and development efforts are directly tied to user needs. * **Improve Traceability:** Link user stories to requirements, test cases, and defects. * **Enhance Collaboration:** Keep all stakeholders (developers, testers, and business teams) aligned. * **Measure Progress:** Monitor the status of user stories and ensure timely completion. ### Planning User Stories in SimplifyQA SimplifyQA provides a structured way to plan user stories by: * **Creating and Organising Stories:** Define user stories and categorise them based on project needs. * **Prioritisation:** Assign priority levels (High, Medium, Low) to manage focus areas. * **Assigning Owners:** Allocate stories to developers and testers for accountability. * **Setting Acceptance Criteria:** Clearly define what constitutes a successful implementation of the story. Planning and tracking user stories in SimplifyQA helps teams stay organised, improve collaboration, and ensure successful product development. By maintaining a structured approach, teams can enhance efficiency and deliver high-quality software that meets user expectations. # Generate Description using AI SimplifyQA provides an AI-powered feature that helps users create or refine **User Story Descriptions** quickly and effectively. This ensures that user stories are well-structured, clear, and aligned with Agile standards. ### How It Works There are **two ways** to generate a user story description using AI: #### 1. Generate from a Goal Prompt * Navigate to the **User Story** section. * Click on the Write with AI button.
* Enter the **goal of the user story** in the provided input field. * The system will automatically create a detailed **User Story Description** based on the given goal. * Click on Insert to add the description.
#### 2. Refine an Existing Description * Enter or paste an existing user story description in the description field. * Click on the Write with AI button and then Generate. * The AI will refine the content, making it more structured, concise, and aligned with Agile best practices. ### Output * The generated or refined description will be displayed in the **Description** field of the User Story. * Users can review, edit, and save the final version. ### **Key Benefits** * Saves time by auto-generating user story descriptions. * Ensures consistency and clarity across all user stories. * Provides flexibility to either **create from scratch** or **improve existing descriptions**. # Generate Acceptance Criteria using AI SimplifyQA leverages AI to automatically generate acceptance criteria based on the user story description. This feature ensures that acceptance criteria are well-structured, precise, and aligned with the intended functionality, reducing manual effort and improving consistency across teams. ### What is Acceptance Criteria? Acceptance criteria define the conditions that a user story must meet to be considered complete. They serve as a guideline for developers, testers, and stakeholders to validate whether a feature works as expected. ### Example of a User Story & AI-Generated Acceptance Criteria in SimplifyQA **User Story Description:** *"As a customer, I want to reset my password so that I can regain access to my account."* **AI-Generated Acceptance Criteria:** * The customer must be able to access the "Forgot Password" option from the login page. * The system must prompt the customer to enter their registered email address or username to initiate the password reset process. * The system must validate the entered email address or username to ensure it exists in the database. * If the provided email address or username is invalid, a clear error message must be displayed (e.g., "Email address not found"). * Upon valid input, the system must send a password reset link or OTP to the customer's registered email address or phone number. * The password reset link or OTP must expire after a predefined duration (e.g., 15 minutes). * The customer must be able to access the password reset page via the reset link or enter OTP to proceed with resetting their password. * The password reset page must enforce security requirements for new passwords (e.g., minimum length, mix of uppercase/lowercase/special characters, no reuse of old passwords). * A confirmation message must be displayed upon successful password reset (e.g., "Your password has been reset successfully"). * The customer must be able to log in with the newly reset password.
### How AI-Generated Acceptance Criteria Helps * **Saves Time:** Eliminates the need to manually write acceptance criteria for every user story. * **Ensures Clarity:** Generates well-structured, testable conditions that align with project goals. * **Reduces Errors:** Minimises ambiguity and ensures all key scenarios are considered. * **Enhances Collaboration:** Provides a clear reference for developers, testers, and stakeholders. ### How to Use AI-Generated Acceptance Criteria in SimplifyQA * **Write a User Story** – Enter the user story description in SimplifyQA. * **AI Processing** – Click on '**Ask AI'**, the AI engine analyses the story and suggests acceptance criteria. * **Review & Edit** – Users can refine the AI-generated criteria to fit specific requirements. ### Frequently Asked Questions (FAQs)
Can I edit the AI-generated acceptance criteria? Yes, you can review, refine, or modify the AI-generated criteria to better align with your project requirements.
Can I disable AI-generated acceptance criteria if I prefer to write them manually? Yes, you can choose to manually define acceptance criteria instead of using AI-generated suggestions.
What happens if the AI-generated acceptance criteria are not relevant to my user story? You can edit or remove irrelevant criteria and provide feedback to improve future AI suggestions.
How do I ensure that AI-generated acceptance criteria align with my business requirements? To get the most relevant criteria, ensure your user story descriptions are clear, specific, and well-structured. You can also customise the suggested criteria as needed.
# Customising Execution with Test Case Level Settings SimplifyQA offers configuration flexibility at two levels: * **Project Level Settings** – Applied globally to all test cases within a project. * **Test Case Level Settings** – Applied only to an individual test case, overriding the default project-level configurations for that specific testcase. This enable users to define custom parameters (e.g., wait times, timeouts, paths) specific to the behavior and needs of a single test case. ### Purpose Test Case Level Settings are particularly useful when: * A specific test case requires longer wait or timeout durations. * A test case downloads files to a unique path. * There is a need to isolate or fine-tune performance for a critical scenario. ### Available Attributes Each setting is defined as a key-value pair. | Attribute | Description | Example Value | | -------------------- | ----------------------------------------------------------- | ------------------------ | | `MINIMUM_WAIT` | Minimum wait time between operations | `1000` ms | | `MEDIUM_WAIT` | Medium-level wait time | `10000` ms | | `LONG_WAIT` | Long wait time for complex processes | `30000` ms | | `MAX_TIME_OUT` | Maximum wait duration for an element or step before failure | `90000` ms | | `IF_TIME_OUT` | Wait time for conditional (if-else) checks | `5000` ms | | `EXIST_TIME_OUT` | Timeout to wait until an element appears | `45000` ms | | `NOT_EXIST_TIME_OUT` | Timeout to wait until an element disappears | `5000` ms | | `DOWNLOAD_PATH` | Custom download directory path for that test case | `D:/Downloads/TestFiles` | {% hint style="info" %} **Note:** All timeout and wait values are in milliseconds. The values override the defaults during test execution. {% endhint %} {% hint style="success" %} **Max Timeout** refers to the maximum duration (in seconds) the system will wait for an element or action to complete during test execution. If the element doesn't appear or the action isn't completed within this time, the step fails. It's useful for handling slow-loading elements or dynamic waits. {% endhint %} ### How to Configure Test Case Level Settings 1. Open the desired test case. 2. Navigate to the Settings tab. 3. Add or update key-value pairs according to your test’s requirement. 4. Click Save to apply the changes. You can also add new rows using the `+ Add Row` button and remove any row if no longer needed.
{% hint style="success" %} * These settings are applied **only** when the specific test case runs. * If a parameter is **not defined**, it falls back to the **Project Level default**. * You can use this feature to experiment with different test environments or performance thresholds without affecting other test cases. {% endhint %} ### Use Case Example Suppose you have a test case that downloads a report which takes more time than usual: * You can increase `MAX_TIME_OUT` to `120000` ms. * Set a custom `DOWNLOAD_PATH` like `C:/Reports/Test1`. This ensures the test case runs successfully without unnecessary delay or failure due to timeout. # Introduction to Test Management in SimplifyQA Test management is a important component of the software development lifecycle (SDLC) that ensures the quality and reliability of your application. SimplifyQA provides a comprehensive platform to streamline and automate test management processes, enabling teams to deliver high-quality software faster and more efficiently. ### What is Test Management? Test management involves the planning, execution, tracking, and reporting of software testing activities. It helps ensure that software meets its quality requirements and provides tools to: * Organise test cases and test suites. * Plan test execution cycles. * Track defects and their resolution. * Generate detailed reports. SimplifyQA offers an integrated approach to managing these activities, making the testing process transparent, collaborative, and efficient. #### Key Features of Test Management in SimplifyQA **Centralised Test Repository** * Store all test cases and test suites in a structured and centralized location. * Reuse existing test cases across multiple projects to save time and effort. **Test Planning** * Define detailed test plans, including objectives, scope, and timelines. * Assign resources and environments for efficient execution. **Test Execution** * Execute test cases manually or automate them using SimplifyQA.\[GS1] * Run test cases across multiple environments and devices seamlessly. **Defect Tracking** * Report and track defects directly within the platform. * Integrate with third party tools for streamlined workflows. **Reporting and Analytics** * Generate detailed reports \[GS2] to monitor test progress, coverage, and outcomes. * Use analytics to identify bottlenecks and improve testing efficiency. **Integration with CI/CD Pipelines** * Integrate with popular CI/CD tools like Jenkins, GitLab, and Bamboo. * Trigger test executions automatically as part of your build pipelines. # Create a Manual Test Case A manual test case is a set of instructions that a tester follows to verify a specific functionality of a software application.It outlines the steps to be performed, the expected results, and the actual results obtained during testing. In this section we will guide you through the process of creating manual test cases within our test case management tool. **Prerequisites:** * A clear understanding of the software feature or functionality you're testing. * Access to the project in which you want to work in SimplifyQA. #### Purpose of Manual Testing * **Uncovers defects:** Manual testing can identify issues that automation might miss, especially those related to user experience. * **Exploratory testing:** Testers can deviate from the script to explore different scenarios and find unexpected issues. * **Usability testing:** Manual testing helps evaluate the software's user-friendliness. * **Initial testing:** Manual testing is often used as a starting point before automation is implemented. ### How to create Manual Test Case? Now let's learn how to work with manual test case in SimplifyQA. There are two approaches to creating manual test cases. Approach 1 : Generate Manual Test Case from User Story 1. **Open the User Story** * Navigate to the **User Stories** section. * Select the desired user story from which you want to generate test cases. 2. **Generate Manual Test Case** * Click on the **Generate Manual Test Case** button.
* The system will automatically create manual test cases based on the details of the user story. * Both **positive** and **negative** scenarios are included in the generated test cases.
3. **Select Required Test Cases** * A list of generated test cases will be displayed. * Each test case will have a checkbox next to it. * Review the list and select only the test cases you want to keep by checking the boxes.
4. **View in Test Case Section** * Once selected, the newly created manual test cases will automatically appear in the **Test Case** section. * You can further edit, execute, or manage them as per your testing needs. Approach 2 : Generate Manual Test Case #### 1. Navigate to Test Case To create a new test case in SimplifyQA, open your desired project and navigate to test case section from the left menu. #### 2. Create a Test Case Locate the '+ Test Case' button and choose 'Manual' and select the desired platform for which you are creating a manual test case.
#### 3. Create Test Steps * For each step, provide: * Detailed step description (e.g., "Navigate to the e-commerce website and browse the product catalog.") * Expected result (e.g., "Website loads correctly, product catalog is visible and functional.") * Parameters: Add Parameters required for the step. Understand parameters in details [here](/introduction-to-parameters).
* Test Data: Provide the data for the parameters added. Learn how to manage data for a test case here [Data Driven Testing in SimplifyQA](/introduction-to-test-management-in-simplifyqa/manage-your-test-data). * Attachment: Upload the required documents, screenshots or any reference files required for a step. * Click the "Add Step" button to add a new test step.
#### 4. **Define Test Case Details:** * Specify the test case name and module and Save your test case. Learn how to organise and manage test cases here [Organise your Test Cases](/introduction-to-test-management-in-simplifyqa/organise-your-test-cases). * **Pre-requisites:** Any setup or conditions required before executing the test case, you can mention them in the form of checklist. * **User Story:** If you are defining the test case for a user story, then you can select the user story. [Learn more ](/introduction-to-test-management-in-simplifyqa/linking-a-test-case-to-user-story) * **Defect:** If you are defining the test case for a defect, then you can select the defect in details section. Learn more {% hint style="success" %} **Additional Tips** * Use clear and concise language in your test steps. * Include screenshots or attachments to enhance clarity. * Consider using a consistent test case template for efficiency. * Regularly review and update your test cases as the software evolves. {% endhint %} #### Purpose of Manual Testing * **Uncovers defects:** Manual testing can identify issues that automation might miss, especially those related to user experience. * **Exploratory testing:** Testers can deviate from the script to explore different scenarios and find unexpected issues. * **Usability testing:** Manual testing helps evaluate the software's user-friendliness. * **Initial testing:** Manual testing is often used as a starting point before automation is implemented. # Create an Automation Test Case **An automation test case is a set of instructions or scripts designed to execute a test scenario automatically without human intervention.** It outlines the steps to be performed, the expected results, and the verification conditions for a particular test scenario. In this section we will guide you through the process of creating automation test cases within our test case management tool. **Prerequisites:** * A clear understanding of the software feature or functionality you're testing. * Access to the project for which you want to create automation test case. * SimplifyQA Wizard needs to be installed and running. Learn how to setup Wizard here [Setup QAWIzard](/simplifyqa-installation-and-setup). ### How to create Automation Test Case? SimplifyQA empowers teams of all technical/non-technical backgrounds to create powerful automation tests without writing a single line of code. Our intuitive platform transforms the way you approach test automation, making it accessible to everyone. Let's explore how you can harness the power of scriptless automation to accelerate your testing efforts and deliver higher quality software. 1. **Navigate to Test Case** To create a new automation test case in SimplifyQA, open your desired project and navigate to test case section from the left menu. 2. **Create a Test Case** Locate the '+ Test Case' button and choose 'Automation' and select the desired platform for which you are creating an automation test case.
3. **Create Test Steps:** * Click the "Add Step" button to start creating test steps. * For each step, provide: * **Object:** * Identify the element on the page (e.g., username text box) and capture the object using [web inspector](/introduction-to-test-management-in-simplifyqa/utilising-web-inspector). Select the captured object in the step. * If you want to re-use the already captured object, locate the object dropdown, it would list the objects available for a particular technology. For Example: If you are creating an automation test case for a web application, for test case type 'WEB' all the web objects would be listed in the object dropdown. You can choose the desired object.
* **Action:** Select the action to be performed on the object (e.g., Click, Type Text, etc). Refer to the [Action docs](/introduction-to-test-management-in-simplifyqa/supported-actions) to understand the supported action in SimplifyQA.
* **Parameter:** Specify required parameters for the action (e.g., text to be typed). Recommended to re-use the parameters available or create a new parameter.
* **Add Test Data:** Define test data that can be varied for different test runs. This allows for [data-driven testing](/introduction-to-test-management-in-simplifyqa/manage-your-test-data).
Sequentially add test steps to create end to end automated test. Design comprehensive test flows by combining various actions and conditions to mimic real-world user interactions. 4. **Define Test Case Details:** * Specify the test case name and module and Save your test case. Learn how to organise and manage test cases here [Organise your Test Cases](/introduction-to-test-management-in-simplifyqa/organise-your-test-cases). * **Pre-requisites:** Any setup or conditions required before executing the test case, you can mention them in the form of checklist. * **User Story:** If you are defining the test case for a user story, then you can select the user story. [Learn more ](/introduction-to-test-management-in-simplifyqa/linking-a-test-case-to-user-story) * **Defect:** If you are defining the test case for a defect, then you can select the defect in details section. Learn more {% hint style="success" %} **Additional Tips** * Leverage the tool's built-in features for [element identification](/introduction-to-script-less-recording-of-test-case-in-simplifyqa/understand-object-recognition-mechanism-and-self-healing) and action recording. * Consider using [test data management](/test-data-management/data-drive-your-test-case) capabilities for efficient test data handling. * Break down complex test cases into smaller, manageable [re-usable components](/introduction-to-test-management-in-simplifyqa/leverage-re-usability-in-your-tests) that can be utilised across multiple test scenarios. {% endhint %} # Learn API Testing API Testing is a crucial part of software quality assurance, ensuring that backend services and integrations work as expected. With SimplifyQA, teams can create, execute, and automate API tests seamlessly, ensuring that applications function correctly across various environments. ### Key Features of API Testing in SimplifyQA * **Create & Execute API Tests:** Define API test cases by configuring requests, headers, parameters, and authentication. * **Validate Responses:** Verify API responses, status codes, and response times for functional correctness. * **Data-Driven API Testing:** Use dynamic test data from different sources to execute API tests with multiple data sets. * **Automate API Tests:** Schedule and integrate API tests into CI/CD pipelines for continuous validation. * **Chain API Requests:** Create dependent API calls where the output of one request is used as input for the next. * **Generate API Test Reports:** Get detailed logs, assertions, and execution reports to analyze API performance and failures. By leveraging API Testing in SimplifyQA, teams can ensure robust service functionality, detect integration issues early, and accelerate release cycles. # Create an API Test Case API testing involves validating the functionality, reliability, performance, and security of Application Programming Interfaces (APIs). APIs are essentially the communication channels between different software applications. By testing APIs, we ensure that these interactions function correctly and securely. ### Prerequisites * A clear understanding of the API you're testing, including endpoints, request/response formats, and authentication methods. * Access to the project for which you want to create automation test case. * SimplifyQA Wizard needs to be installed and running. Learn how to setup Wizard here [Setup QAWIzard](/simplifyqa-installation-and-setup). ### How to create an API Test Case? Take your API testing to the next level with our comprehensive guide. In this section learn how to create robust and efficient test cases, leverage advanced features, and optimise your testing process. 1. **Navigate to Test Case** To create a new API test case in SimplifyQA, open your desired project and navigate to test case section from the left menu. 2. **Create a Test Case** Locate the '+ Test Case' button and choose 'Automation' and select the API for creating an API test case.
3. **Construct the API Request:** * Select the HTTP method (e.g., POST, GET, PUT, DELETE). * Enter the complete endpoint URL in the designated field as shown below 4. **Define Request Parameters:** * Under the "Params" tab, specify any query parameters required for the API request. * Provide the key, value, and optional description for each parameter. 5. **Set Authorization:** * If the API requires authentication, configure the authorisation method (e.g., Basic, Bearer token, API key) under the "Authorisation" tab. * Provide the necessary credentials or tokens. 6. **Add Request Headers:** * Under the "Headers" tab, specify any additional headers required for the API request. * Provide the key, value, and optional description for each header. 7. **Construct Request Body:** * If the API requires a request body, define its structure under the "Body" tab. * Use appropriate formats like JSON, XML, x-www-form-urlencoded, form-data, etc. * You can define your JSON and the JSON editor would allow you to beautify the JSON and also you can add comments for reference. # Quick Test the API This section will help you quickly test APIs using a simple editor interface. By following these steps, you can easily evaluate API functionality, analyse responses, and identify potential issues. ### How to test the API? To quickly test the API endpoint, you have to first provide all the input parameters in the API editor. To learn how to user the editor to create API test case, refer to [Create an API Test Case.](/introduction-to-test-management-in-simplifyqa/learn-api-testing/create-an-api-test-case) 1. **Pre-Requisites:** Create the API step with the required input details of the endpoint in the API Editor. 2. **Click the "Send" Button:** Once you've configured the request, click the "Send" button to execute the API call. 3. **Analyse the Response:** Examine the response that appears in the designated area. This response includes: * **Response Body:** Data that is returned by the API in response to a request. * **Status Code:** Indicates the success or failure of the API call (e.g., 200 for success, 404 for not found). * **Headers:** Additional information about the response, such as content type or authentication details. * **Body:** The data returned by the API, which may be in various formats like JSON, XML, or plain text. The format of the response body can vary depending on the API's design and the specific request, but common formats include: * **JSON (JavaScript Object Notation):** A lightweight data-interchange format that is widely used in APIs. * **XML (Extensible Markup Language):** Another popular format for data exchange, often used in older APIs. * **Plain text:** A simple format for returning text-based data. * **HTML (Hypertext Markup Language):** Used for returning web pages or other HTML-based content. When testing APIs, it's important to examine the response body carefully to ensure that it contains the correct data and is formatted as expected. # Validating API Responses Assertions are used to validate the response from the API and ensure that it meets the expected criteria. This section will guide you through the process of adding assertions to your API test cases. * **Navigate to the Test Case:** * Navigate to the API test case you have created or [create a new API test case](/introduction-to-test-management-in-simplifyqa/learn-api-testing/create-an-api-test-case). * **Quick Test the API:** * Click on 'Send' button to run the API call and wait for the response. * **Open Assertions Section:** * Once you have the API response. Click on the "Assertions" tab within the test case. * **Define Assertion:** * Select the assertion type from the dropdown (e.g., Received Response). To add assertion on response header. Select 'Received Headers' from the assertion type dropdown. * Choose the condition for the assertion (e.g., Equals, Contains, Greater Than). * Actual Value will be auto-captured from the received response. Enter the expected value for the assertion. You can also [parameterise](/introduction-to-test-management-in-simplifyqa/learn-api-testing/understanding-api-parameterisation) the actual value to validate the dynamic values. * Select the checkboxes to add assertions. * **Review and Save:** * Review all assertions for accuracy and completeness. * Click the "Save" button to finalise the test case. * **View Assertions** * To review the added assertions, navigate to 'View Assertions'. * History of all the added assertions would be captured in 'View Assertions' section. For example, if there are keys in response which dynamically appears in specific scenarios, you can view those added assertions in this section. * **Delete Assertions:** You can choose the added assertions and delete the assertions which are not required. **Example:** Here's an example of an assertion. It is important to add assertion on status code irrespective of positive or negative scenario, as it helps to identify immediately if the API fails. * **Assertion Name:** Status Code * **Condition:** Equals * **Expected Value:** 200 * **Actual Value:** Value from the API response {% hint style="success" %} **Additional Tips** * Add multiple assertions to verify different aspects of the API response. * Parameterise to validate dynamic values in the API reponse. {% endhint %} # Understanding API Parameterisation **API Parameterization** is the process of dynamically inputting values into API requests during test execution. It allows you to test APIs with various input combinations, ensuring comprehensive coverage and identifying potential issues that might not be detected with static values. Dynamically data drive your API by parameterising the API request. To parameterise type '{{' to get the list of parameters. You can add a **local parameter** to data drive the API request and provide the test data manually **Global parameter** would be used when you have stored the value globally for easy management and reuse across multiple test cases. **For Example**: Endpoint URI would be a constant which would be used globally across multiple test cases in a project. ``` https://reqres.in/api/users?page=2 ``` In the above Endpoint URI, it can be parameterised with a global parameter as ``` {{Endpoint_URI}}?page=2 ``` In this case, 'Endpoint\_URI' would be a global parameter with a constant value ''. **Runtime Parameters** would be used to extract values from previous API responses or generate dynamic data and use them as parameters in subsequent calls. **Example 1 :** In case of Login API, you would be receiving a authentication token in the API response. You can [extract](/introduction-to-test-management-in-simplifyqa/learn-api-testing/achieve-data-flow-for-e2e-testing) the token from the API response and store it in a runtime parameter. Now you can use this runtime parameter in subsequent API call or any other test case. **Example 2 :** If a data has to be dynamically generated such as, userID or orderID to get a realistic data - generated data would be stored in a runtime parameter. Now you can use this runtime parameter in subsequent API call or ay other test case. {% hint style="success" %} **Additional Tips** * **Clear Naming Conventions:** Use meaningful names for parameters to improve readability. * **Data-Driven Testing Best Practices:** Follow best practices for designing and managing data-driven test cases. * **Environment Variable Management:** Securely manage sensitive parameter values in environment variables. {% endhint %} # Save API Response Data Effectively manage and analyse API response data within our test case management tool. Capture essential details like response status, response code, and response body for in-depth analysis and validation. In this section you'll learn how to save the various response data to validate the API response. #### Save API Response * To save the entire API response, locate the 'Save' option in the response section and select 'Save Response' to save the entire API response payload. * Assign the extracted value to a parameter for later use. You can also create a new parameter of type [runtime](/introduction-to-parameters/understanding-runtime-parameters) and assign. * After storing the API response, you can custom validate the response key and value, JSON Array and JSON Object using [custom methods](/code-editor). #### Save JSON Key * Effectively handle dynamic JSON keys within API responses by using "Save JSON Key". * Determine the JSON key that appears dynamically within the API response and select the "Save JSON Key" option. * Specify the JSON path to the desired key using a valid JSONPath expression. Assign the extracted value to a parameter for later use. You can also create a new parameter of type [runtime](/introduction-to-parameters/understanding-runtime-parameters) and assign. **Example:** **JSON Response** In below example JSON key to save email which occurs dynamically in the response would be ``` JSON Path: response.data[1].email ``` ```json { "page"📑: 2, "per_page"📑: 6, "total"📑: 12, "total_pages"📑: 2, "data"📑: [ { "id"📑: 7, "email"📑: "michael.lawson@reqres.in", "first_name"📑: "Michael", "last_name"📑: "Lawson", "avatar"📑: https://reqres.in/img/faces/7-image.jpg }, { "id"📑: 8, "email"📑: "lindsay.ferguson@reqres.in", "first_name"📑: "Lindsay", "last_name"📑: "Ferguson", "avatar"📑: https://reqres.in/img/faces/8-image.jpg }, ], "support"📑: { "url"📑: https://reqres.in/#support-heading, "text"📑: "To keep ReqRes free, contributions towards server costs are appreciated!" } } ``` #### Save Response Status Code, Size and Time When you run a API request in the API Editor, API response should contain response status code, size and time. To save this response data and validate in the same test case or some other test case, click on the respective response and assign the extracted value to a parameter for later use. You can also create a new parameter of type [runtime](/introduction-to-parameters/understanding-runtime-parameters) and assign. # Achieve Data flow for E2E Testing Effectively manage and reuse dynamic data extracted from API responses to streamline your API testing. Our tool allows you to store key-value pairs from API responses for subsequent use within the same test case or across multiple test cases of different technology. In this section, you'll learn how to store the response value and re-use them along with some examples. #### Storing Values 1. **Identify Target Data:** Determine the specific key-value pairs you want to extract from the API response and select the save option. 2. **Store in Variable:** Assign the extracted value to a parameter for later use. You can also create a new parameter of type [runtime](/introduction-to-parameters/understanding-runtime-parameters) and assign. #### Reusing Stored Values After storing the required values from the API response, you can use the stored values as: 1. **Reference Variable:** In subsequent test steps or other test cases, reference the stored variable using its name. 2. **Dynamic Parameterisation:** Utilise variables to create dynamic test data and enhance test coverage. 3. **Cross-Test Case Dependency:** Pass values between test cases to simulate real-world scenarios. To use the stored values, navigate to API editor and type '{{'. Select runtime parameter and choose the parameter in which the value is stored. [Learn more.](/introduction-to-test-management-in-simplifyqa/learn-api-testing/understanding-api-parameterisation) Click on 'Send' to send the API request and get the response in the editor. By effectively utilising this feature, you can significantly improve the efficiency and reliability of your API test automation efforts. # Create a Database Test Case **Database testing** is a critical aspect of software quality assurance that focuses on verifying the correctness, integrity, and performance of a database system. It involves testing various aspects of the database. Database automation testing involves creating scripts or code that can automatically execute database queries, validate results, and report on test outcomes. This can be achieved using various tools and programming languages. ### Prerequisites * Access to the project for which you want and privilege to create data base automation test case. * Necessary Database connection details (host, port, database name, username, password). * SimplifyQA Wizard needs to be installed and running. Learn how to setup Wizard here [Setup QAWIzard](/simplifyqa-installation-and-setup). ### How to Create a Database Test Case 1. Navigate to **Test Case** from the left-hand panel.
2. Click on '**+ Test Case'**. 3. From the **Automation** dropdown, select **Database**.
4. Enter a meaningful **Test Case Name**. 5. In the **Action** section of each step, select the appropriate [database action](/introduction-to-test-management-in-simplifyqa/supported-actions) (e.g., *Connect to DB*).
6. In the **Parameter** section, input the required [parameters](/introduction-to-parameters/create-and-utilise-parameters-in-your-test-case) details which will be prompted (e.g., *Database Type, Host, Port, Username, Password, Database Name*)
{% hint style="info" %} The Test Data for the parameters can be added from the Test Data Tab. Database Type should be all in capitals e.g., POSTGRES or MYSQL. {% endhint %} 7. After establishing the connection, you can directly input your **SQL queries**. Each query and its corresponding assertion can be saved as a separate step. 8. Arrange these steps in the desired sequence to define the test case flow. Once all relevant steps are added, click **Save** to finalise the test case and select the appropriate module. ### Use Case: Create, Insert, Update & Validate Data in PostgreSQL Database **Objective:**\ To validate the creation of a database table, insert multiple records, update a specific record, and confirm the update via query validation. #### **Steps Overview:** 1. Establish Database Connection * DB Type: PostgreSQL * Host: `64.227.131.72` * Port: `5432` 2. Execute a SQL query to create a table named `Simplify` 3. Insert test data into the newly created table 4. Read Data for Validation * Use a Read Query action to retrieve current data from the `simplify` table. * Store the result in a Runtime Parameter for validation. 5. Update a specific record’s last name 6. Read Updated Data for VerificationExecute another Read Query to validate the updated `last_name` * Again, store this result in a Runtime Parameter to verify if the `last_name` has changed to `Doe-Smith`.
**Validation Outcome:** This test case validates: * Successful table creation * Accurate data insertion * Proper update functionality * Reliable data retrieval for assertions Database test case in SimplifyQA empowers users to validate backend data operations efficiently without the need for complex scripting. With a user-friendly interface, support for various databases, and step-wise execution flow, testers can quickly connect to databases, run queries, assert results, and ensure data integrity. Whether you're validating application behavior or performing backend regression testing, SimplifyQA makes it seamless to integrate database validation into your automation strategy. ### Frequently Asked Questions (FAQs)
What types of databases does SimplifyQA support? SimplifyQA supports all major structural and non-structural databases.
Can I use multiple queries in a single test case? Yes, each query can be added as a separate step in the test case. You can organise them in the required sequence.
What if my connection fails during the test execution? The execution log will capture connection errors. Make sure host, port, credentials, and firewall rules are correctly configured.
--- [Next Page](/llms-full.txt/1)