I've configured the station options, report options, global variables, etc. but it seems that they are not saved in a workspace or sequence file.
I found where those get stored in these forum: https://forums.ni.com/t5/NI-TestStand/Export-Report-Options-in-Sequence-file-deployment/td-p/3062172...
Is there a way to import these configurations into teststand? we have several people working on the same project on different computers. we are using GIT as a source control and to share the progress, how can we share the configuration of teststand?
I would highly advise against sharing TestStand configuration. You will run into more problems than you will solve. Trust me on this one...I've been there and tried that for like 2 days. The problem is that they get saved so often (serioulsy every time you open and close TestStand) that everyone will be bombarded with dialogs and other warnings.
However, environments are a great way for someone to get their machine into different states quickly. You could set a baseline for each project and then when someone moves to a different project they could copy down and use that project's environment.
Hope this helps,
Ok So I was able to create an environment but then how can I import or copy that environment i created to a workspace? What I mean is how can another person use that environemt I created in their workspace, how can they import it?
you cannot use it in a workspace. The cfg gets loaded when the engine starts, long before workspaces are loaded.
You could put it on a shared drive and create a shortcut to TestStand that loads that environment. Or you could distribute with source code control, like GIT.
I want to make it very clear though. It is a bad idea to share configurations. Developers will continually be tromping on each other's cfg files because like I said earlier, TestStand is constantly writing them.
My recommendation is that you get it set up how you like it and create a .nipkg that will install it to a certain location including a shortcut that loads a certain environment. That way people working on the project will just need to install that package and click ont he shortcut.
This link shows how to start the sequence editor with a defined environment:
You can just create a shortcut on your desktop, or wherever, and pass that argument to the sequence editor.
As for NIPM you are opening a whole new can of worms there. If you aren't currently using it then you might not want to move to it. Instead of a .nipkg you can just us a batch file to copy the folder you need to the proper locations on the local machine.