Hi,
I am testing sahi execution with bundle, e.g. adding an include and trying to execute the file.
It appears that it is not working.
the file are correctly loaded into the temp directory,
but the include is not done with the correct parameter I guess.
I have :
in my sahi file.
_include('dir/include.sah');
And ta file :
LOAD sahi.sah AS sahiParameteredTestSource
CONVERT sahiParameteredTestSource TO script.sahi(script) AS Testxxx.bundle
LOAD testfirefox.properties AS testff.file
CONVERT testff.file to properties(structured) AS ff.properties
TEST :
EXECUTE execute WITH _Testxxx.bundle ON jadetest USING ff.properties AS testxxx.result
ASSERT testxxx.result IS success
In the EXECUTE bundle, there is a parameter USING (mainpath....)
But I couldnot find what it should match.
I can see a dir_ta_XXXXX in the temp directory, but none in the sahi3928383236490042672bundle directory
So I am wondering if there is something I have to do in order to get it work.
Thanks for quick reply.
And btw, have any of you tested to load a sahi suite ?
I think it would be great to have it work. But one step at a time.
When I can LOAD Files from a directory and include properly, things will be great.
Testing sahi bundle and question about suite files
-
- Messages : 28
- Inscription : mar. déc. 13, 2016 3:02 pm
Aller
- Présentez-vous / Introduce yourself
- Squash
- ↳ Exigences / Requirements
- ↳ Cas de test / Test cases
- ↳ Campagnes / Campaigns
- ↳ 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