Answered

How to use the Export feature in Subject7

William Smith

November 11, 2021 20:34

I was reviewing the Export feature in Subject7. I was successfully able to export a test case which created a zip file on my local system.

When I tried reviewing the files created I was unsuccessful.

Using the unzip tool, I received the following error messages on the files "unsupported compression method 99". The unzip command did create the directories which were in the archive but no files "artifacts", "function", and "tests".
I also tried the windows 10 "Extract All" command which is part of the file browser and received an unexpected error. Again, the extract created the directories.

7zip was able to create the file names, but they were all empty.
So, 4 questions.

     What is the purpose of the Export feature?
     What is the file format of the files created?
     How do I read those files?
     Is there a way to add the Exported data back into Subject7?

5 comments

Rex Feizi November 11, 2021 20:41

The zip file is encrypted, that is why you or anyone else can see the content.

1. The purpose of the export feature, is to transfer assets between different accounts meaning import/export. For example, some organizations have 2 Subject7 installations prod/stage, and they want to transfer tests/artifacts between the two installations. Or for example for sharing amongst users from different accounts.

2. The format is encrypted ZIP.

3. You cannot read the content. Any particular reason why you want to?

4. Yes, you have to have permission and you can find the import on the root of the test library. However, on the same installation (instance of subject7, or account), it doesn't make sense. Please elaborate on your goal maybe we can help.

William Smith November 11, 2021 21:16

Thanks Rex. That is useful. To answer your question.

As we progress through different versions of our products we make changes to Subject7 tests. These changes include updates to locators, functions, etc. I am still looking for efficient ways to make these updates without destroying the ability to go back and test previous revisions of the product.

One thought I had with the export feature was to save off a version of the tests and the items the test calls and preserve them in case we want to use them later.

We are still struggling with good techniques for a good versioning system for Subject7. Something where we can make updates to tests, functions, and locators in an efficient way and not destroy the functionality for executing testing on previous releases. One thought with the export idea was to export the tests functions and locators, then write scripts to re-name the functions to match the current tested product release.

Rex Feizi November 11, 2021 22:06

Wow! The timing is great. We just released a beta version of our versioning and Project Management (PM) capabilities.

I could set up a call and go over the basics with you. Also, I can give you an account as a beta user in our cloud.

Alternatively, if you want to see how your data will work with our versioning/PM capabilities, then we have to get permission to host it on the test server local at NHLBI.

Looking forward to your response.

William Smith November 12, 2021 18:56

Rex: I am looking at my options here. What is the expected release date for the new capabilities?

Rex Feizi November 13, 2021 16:55

The goal is January 15th, However, we are gathering feedback from our beta users and partners. Depending on how thick of feedback we receive, it may vary.

Meanwhile, I think you can get started transferring assets to contained projects and baseline them in the platform as early as next week. In other words, you can divide the flat structure into different projects, define groups that have access ot them, make sure they are ready to be versioned.

Please let me know if we can have a meeting so we can go over the architecture, capabilities, enhancements, etc.

Please sign in to leave a comment.