Kiwi TCMS: location of tcms.conf file to link RobotFramework robot files to Kiwi TCMS test cases for test execution reporting in Kiwi TCMS - kiwi-tcms

I am new to Kiwi TCMS.
My Manager installed the Kiwi TCMS and assigned me to a Test group.
I have used Visual Studio Code to create my RobotFramework test files.
I would like to setup my RobotFramework tests to link to the test cases I created in Kiwi TCMS in order that I can execute the Robot tests cases (automated) and they link to the relevant test case in Kiwi TCMS and a report can be done on test execution etc.
I have installed the Kiwi TCMS RobotFramework plugin in the Visual Studio Code.
With regard to the tcms.conf file - is this a file that should already be present and in the home directory e.g. C:\Users\username- and if so, would this be available to myself as a Test group user or would my Manager only have access (as he setup/installed Kiwi TCMS)

I read the documentation. And I already appear to have the tcms-api installed on my home directory\appdata\local\progams\python\python39\lib\site-packages. With the .tcms.conf file do I create this within an editor like Notepad++ or some other editor as I am using Visual Studio Code, and place on my home directory or is it something I generate in the command prompt ?? Apologies I am new to Kiwi-TCMS and this kind of thing. – TinaTest Mar 3 at 10:52
Are you able to assist with this query, please? As I need to try and get this working asap. Many Thanks. –

Related

Avoid write manually Test Cases with Kiwi-tcms

Is it possible to write automatically test cases with the tool kiwi-tcms ?
write the automated code for testing and then connect it to the Kiwi API to send that test case ?
https://kiwitcms.org/
https://kiwitcms.readthedocs.io/en/latest/plugins/automation-frameworks.html
Kiwi TCMS can be used with test automation frameworks. Test names and results are fetched automatically from the test automation framework using a plugin! This is an additional software package that you have to install in your test environment and configure it to talk back to Kiwi TCMS.
Available plugins
tap-plugin: for reading Test Anything Protocol (TAP) files. Written
in Python
junit.xml-plugin: for reading junit.xml formatted files.
Written in Python
Native JUnit 5 plugin written in Java
Robot Framework plugin
Django test runner plugin

How to deploy a winforms application into Azure DevOps

I am looking for a step by step guidance to deploy a c++ winforms application into Azure DevOps.
I have a legacy application and its already into TFS server but now the team has planned to put it into Azure DevOps and automate the builds and release process.
I did some researches and tried something and it partly worked out. But, I cannot understand whether to go by GIT or TFVC (Team Foundation Version Control)?
As, the application is already into TFS, I believe it will be easier to create the repository and pipeline using TFVC. But, what if I want to do using GIT? What are the factors I should consider when using GIT?
NOTE: I do not have TFS server access but I do have Azure DevOps access.
What I have tried:
Created a demo project. Below are the details about the demo project:
<code>Project and Solution Name -> SampleApp
Solution file location -> "C:\SampleProj\SampleApp\SampleApp.sln"
Other project files location -> "C:\SampleProj\SampleApp\SampleApp"</code>
Tried to deploy the above sample project into Azure, using GIT. The steps I followed are given below:
<code>
1. Installed GIT.
2. Logged into dev.azure.com with my credentials.
3. Created a new project and copied the 1st link as provided in "Repos" section.
4. Created a ".gitignore" file from Visual Studio Team Explorer -> Settings -> Repository Settings.
5. Went to the project folder (C:\SampleProj\SampleApp\SampleApp\) and right-clicked and selected "GIT Bash Here". The GIT command prompt opened up and typed the following commands:
a. git init
b. git remote add origin [URL copied at step 3]
c. git add .
d. git commit
e. git push -u origin master
</code>
After these steps, the repos in Azure were holding all the files except the solution file (.sln) and when I created pipeline for builds, the builds started to failed as it was not getting the .sln file.
I cannot understand the below mentioned points:
<code>
1. For all projects, I cannot find Repository Settings in Team Explorer. Why so?
2. If I have a legacy application already in TFS, can't I make it done using TFVC instead of using GIT?
3. What are the correct steps being followed in the industry?
</code>
I did some researches and tried something and it partly worked out.
But, I cannot understand whether to go by GIT or TFVC (Team Foundation
Version Control)?
Git is distributed system while TFVC is centralized system. More into about their difference you can refer to this document.
But, what if I want to do using GIT?
About moving from TFVC to Git you can consider using git-tfs tool. More details check this guide.
Tried to deploy the above sample project into Azure, using GIT. The
steps I followed are given below:
If you have a newly created project, you can easily add it into git source control in Visual Studio and then push it to Azure Devops Service project. Please check Share your code with Visual Studio 2017 and Azure Repos Git.
For all projects, I cannot find Repository Settings in Team Explorer.
Why so?
You need to add the solution into source control in VS first, then you can find repository Settings in Team Explorer=>Settings=>Repository Settings.
Hope all above helps and it could be better to separate the different questions in your post into different threads.

Can we write test cases in excel and upload into Kiwi tcms

I just started using Kiwi TCMS and i do not find an option to upload an excel into Kiwi TCMS.
I can only create one test case at a time which is consuming time for me. So i want to write the cases in an excel sheet and then upload it to Kiwi TCMS.
Answer is NO, you can't import Excel files directly, see the docs here:
https://kiwitcms.readthedocs.io/en/latest/import-export/index.html
Another user had started working on an import script mentioned at:
https://github.com/kiwitcms/Kiwi/issues/1104
If you decide to write something by youself please be a good open source citizen and contribute it back to our api-scripts repository (all mentioned in the docs).
To speed up writing process you can use the "Clone" functionality when writing test cases or parse/import from existing sources using the API.

Launch remote process for automated test using Kiwi tcms

Is it possible to have a kiwi-tcms test case launch an executable on a remote server in order to execute the test case and if so how could that be done ?
Short answer - NO!
Long answer:
what you are looking for is some kind of test runner or CI system - that will connect to a remote computer (or use an API directly) and launch automated test cases based on some parameters.
This brings up so many questions I can't even list all of them here but some of the most important ones:
who/where we store authentication credentials
how are progress and results monitored and reported
when are tests scheduled ? What kind of triggers are supported/desired ?
Kiwi TCMS takes a different approach when dealing with automated tests. You can schedule your tests in any way you like and then report the execution results back to Kiwi TCMS.
We are working on plugins for popular test runners, like JUnit, Python Nose, etc, that will automatically discover the result and name of your automated test cases and report them back to Kiwi TCMS.
If you do need a specific plugin/framework please open a request on GitHub and our team will take it into consideration.
Edit: upvote, comment & follow this feature request at https://github.com/kiwitcms/Kiwi/issues/914
I needed to do something similar: run automation on remote systems and report results back to Kiwi. I put together several components to get the entire system working. Here's what worked for me:
Jenkins to initiate test runs and manage remote machines
A Python script to create test runs against a test plan and write out a custom test run manifest, which is...
Passed to the automation system (.NET/C#) via more scripts to make sure the remote machine is configured correctly
Automation output is directly consumed by Jenkins to report test results for the build/job as well as consumed by another Python script that pushes results back to Kiwi
The automation system knows how to interpret the test run manifest and map test cases to test methods implementing the test. It's important to include the Kiwi caserunid throughout the pipeline so the result is associated with the correct Kiwi entry.
please open feature requests on GitHub if you'd like to get test runner adapters (essentially plugins) for Kiwi TCMS. GitHub is the only place where we can track who needs what and prioritize!

Click Once: Auto Select Publishing Location and Installation URL based on Config(Debug,QA,Release)

I would like to be able to publish from visual studio. I am able to do this
I have different configurations for Debug,QA,Release. I am using config transforms and they work fine.
ISSUE: when I publish the I want the Debug, QA,Release to be published to their respective folder example E:\Application\Debug and so on. I am able to do this by changing the Publishing folder location and Installation folder location manually. How can this be such: f I change the configuration these locations are selected automatically. So when I need to publish a particular version -> and all I need to do is
change the config
press the publish now button.
Thanks!
The only possibility I know of would be to use a Build Server and build if the Source code changes (probably seperate branches) and have build definitions for each case.
This would mean that you would have to have a kind of source control (Git, Mercurial, TFS) for the Project and the resources to run that kind of service or use a Service on the internet.
Build Server for local installation:
TeamCity
Team Foundation Server
Build Server via Internet:
VisualStudio.com
(Those are the onse that come to my mind because I have used them before. There are much more available)

Resources