Hi
I am trying to set up a project for CRM product testing for testing multiple application products that are similar in use/functionality. For example Product A, Product B, and Product C.
I want to set up a series of categories - each using the same set of test cases by category. For example Category A, Category B, Category C.
Different groups of users will perform the same testing for each product and category combinations. For example Product A - Category A, B, & C and Product B - Category A, B, C.
The testing may be done in one or multiple phases. For example Phase 1 may be Configuration, Phase 2 may be Process, and Phase 3 may be Reporting. All of the phases would be the same for each Product.
For each test case, I want to score two items - Functionality and Usability with the scores being 0 through 4 for each test case. So for Product 1, Category 1, Test Case 1, one user may score Test case 1 with a 1 and a second user may score Test case 1 with a score of 2. And. For Product 2, Category 1, Test Case 1, the same first user may score Test Case 1 with a 2, and the second user may score Test Case 1 with a score of 2.
I want to be able to average the Functionality and Usability scores for Product 1, Category 1, Test Case 1 across all users. So for Product 1, Category 1, Test Case 1, the total score would be 3 with an average of 1.5. For Product 2, Category 1, Test Case 1, the total score would be 4 with an average score of 2.
What is the correct way to set this structure up?
Thanks
Steve
First Project
Revenir à « Questions générales / General questions »
Aller
- Présentez-vous / Introduce yourself
- SquashTM
- ↳ Exigences / Requirements
- ↳ Cas de test / Test cases
- ↳ Exécutions / Executions
- ↳ Pilotage / Management
- ↳ Administration
- ↳ Bugtrackers
- ↳ Xsquash
- ↳ Installation & Base de données / Installation & Database
- ↳ API Rest Test Management
- Support des tests automatisés
- ↳ Version alpha
- ↳ Conception / Design
- ↳ Écriture tests au format BDD / Writing BDD test cases
- ↳ Gestion bibliothèque d'actions / Management action library
- ↳ Realisation
- ↳ Workflow d'automatisation / Automation workflow
- ↳ Rapports HTML / HTML reports (format Allure)
- ↳ Transmission de paramètres
- ↳ Implementation
- ↳ Association scripts de test - cas de test manuels / test scripts - manual test cases
- ↳ Création de plan d'exécution "as code" / Creation of execution plan "as code"
- ↳ Execution
- ↳ Pilotage de tests automatisés / Management of automated test execution
- ↳ Historique des exécutions automatisées / History of automated runs
- ↳ Gestionnaire de code Git / Git code manager
- ↳ Technologies d'automatisation de tests
- ↳ Junit
- ↳ Cucumber
- ↳ Robot Framework
- ↳ Cypress
- ↳ SoapUI
- ↳ UFT
- ↳ Ranorex
- ↳ Agilitest
- ↳ Katalon
- Intégration à la CI/CD
- ↳ Version alpha
- ↳ Déclenchement des "plans d'exécution as code" dans Jenkins / Triggering execution plans "as code" in Jenkins
- ↳ Intégration des "plans d'exécution as code" / Integration of execution plans "as code"
- ↳ GitLab CI
- ↳ Azure DevOps
- ↳ AWS CodeBuild
- ↳ Cloudbees CI
- ↳ Xebia Labs XL
- ↳ Execution
- ↳ Récupération des plans d'exécution et paramètres / Retrieve predefined execution plans and parameters
- ↳ Exploitation des résultats dans Allure EE / Exploitation of the results of automated executions in Allure EE
- Gestion de la communauté / Community Management
- ↳ Contributions
- ↳ Questions générales / General questions
- ↳ Propositions d'évolution / Ask for new features
- Squash TF
- ↳ SKF et rapports / SKF and reports
- ↳ SKF
- ↳ Reporting
- ↳ SKF Plugins
- ↳ Sahi Plugin
- ↳ Database plugin
- ↳ FTP Plugin
- ↳ SSH Plugin
- ↳ Filechecker Plugin
- ↳ Selenium Plugin
- ↳ SoapUI Plugin
- ↳ Local Process Plugin
- ↳ IDE Plugins
- ↳ TA Toolbox & Installation
- ↳ Installation
- ↳ TA Toolbox
- ↳ Eclipse Plugin
- ↳ IntelliJ Plugin
- ↳ Squash Execution Server
- ↳ Lien cas de test - tests automatisés / Test cases - automated tests link