Go to Shared Documents
Click Manage Folders
Add a new folder
Check the Public Folder checkbox (Check this if you want to use Security Group – Shared Document privileges to setup default Folder privileges for each user in this project.)
Click the people icon to manage security rights
Make changes & click Submit Changes
(by the way, why is the user creating the folder and editing the privileges on the list? What if I accidentally unchecked my full access box? Then I wouldn’t be able to access the folder at all. Dangerous).
Result: Screen flashes but no confirmation message that changes were applied
Expected: Confirmation message that changes were applied
Can you please reduce the SmartBear Banner at the top of the page. This will enable us to see more of what we have purchased the product for..
Can you also reduce the of the Customer Company logo box (bottom left hand corner). It's nice to have our logo on screen but if we can configure the size of the box or turn it off it makes the product more usabale.
We would like to the ability to specify an existing Test within a csv and import new Test Steps for it. Below is our use case for this request.
For our implementation of QAComplete, we are using a staged rollout. That is, we are creating Tests without Test Steps and executing the corresponding Test Sets. We are doing this due to the time constraints and resource limitations to entering the large volume of tests and the varied state of testing documentation throughout the organization.
There are only 2 ways to link a test to a configuration...either
1. select the test (or test set), open the link to items, select the configuration folder, and check each sub item (e.g. Windows8>IE, and Chrome and Firefox), repeating for each config folder.
2. select the configuration, open the link to items, specify type and folder, and individually check every item (test) in the folder. Repeat for every configuration.
Even with just a few Windows environments, each with 3 or 4 different browsers, times our 2500 tests, and this is a monumental task. While we could have done it as we created tests, our focus was on creating the tests, and not linking..that was a mistake.
However now, we need to make these links, yet we are looking at nearly 10,000 clicks/steps.
If nothing else, in the selection of tests (or sets) drop down, add a "Select All" to check all tests in that folder. Then we would just need to repeat for each Configuration, each folder...a much more manageable task.
There are many things that I use shared documents for. Some documents I need to link to requirements, some to tasks, some even to test case steps. I want to store documents in a shared location and then be able to link them wherever I want in the application. I also want the link to just reference the newest version of the document.
For example, I have a new team member doing their training. I create a task to review our documents on process. Before they get to doing that task, I change a part of the process document, but I want the new team member to see the most updated copy.
Currently I have a few options:
1) Upload the document directly to the task, and have to remember all tasks that have that document attached and re-upload everytime something changes (Not a good Solution).
2) Upload the document in the shared documents folder and tell them where to go find it which could also change (Not a good solution)
3) Upload the file in the shared doc section and use the url path generated there to link it to the task - however, if the document updates the url link is no longer a valid link.
4) Create an entirely new website to store all my files and use the UNC Path from that website to link it back to tasks and shared docs and tasks. This seems kind of rediculus considering in the software there is a shared document section.
Consider another scenario:
I have a lot of test cases that have SQL instructions in them. When the database is updated, I don't want to go edit text everytime with new SQL in all the test cases. This could be solved by creating reusable components for tests (this I think has already been suggested). Or allowing me to upload a text file for SQL that I could attach anywhere I wanted that specific SQL run for a test case. When I update that SQL it would then update all test cases.
Thanks - and if anyone has any solutions to this information sharing issue I would love to hear them!
I'm preparing for a release and adding in many folders and sub-folders. Please improve the UI such that the screen doesn't need to refresh after each folder has been created.
It would be more efficient to have a modal appear (when adding multiple folder/sub-folders) with a "Add & Create Another" type of form.
We often copy test cases between projects using the Fast Edit - Copy Items from One Project to Another, and would love for the destination project/folder window to stay open when the user selects another folder to copy from. Currently, the destination widow closes if another folder to copy from is selected. This can make it incredibly time consuming to copy tests from multiple folders into a different project.
Jamie @ DSW Inc.
It could be beneficial to have a special custom field whcih gave the ability to fetch values from an external database.
it could have a connection string attached and based on that you could get values based on a SQL query.
this would give issues a more dynamic way of showing data.
Ole Keiser Christensen
When starting tests from test sets, the only way to view a tests description is to open the print preview.
However since our tests usually have a lot of different preconditions (e.g. which database to use or which steps to prepare) we need the description quite often.
It would be very helpful if a tests description and notes were accessible more quickly in the test runner.
This would allow creation of a super Test Set, made up of other test sets without having to add each test to it individually, and prevent having to update multiple test sets when one test is added.
Currently (QAC 11.0 or older) in order to get complete Release report for example, you need to link manually all requirements and test cases which are in scope for this release.
In our team we assumed logically that if you have Test sets associated to test cases and you map these Sets to a release the Tests scenarios will be automatically associated with this release.
If we have to run say full regression testing of all existing test cases in one release (like few thousands), that means that we have to link manually all these test cases to the release.
The link between the above work items should em improved and automated.
In the Test Library, I can display all tests linked to a release or not linked to a release by using a filter. This is not intuitive to many of our testers. To be consistent with the other entities in the system, it would be helpful to have a Releases tab in the navigation pane on the left before the Folders tab as is the case for Test Sets.
I would like to be able to select an option in QA Complete for it to assign test runs to the next available host from my pool of test hosts rather than limiting test runs to one specific host, this is not an efficient use of resources.
We need the ability to add custom fields to the Test Runner. When we test for a release, new builds are continously created and are used by various departments/individuals to test against. We need to record which build was used during each test run. We also need to be able to record which environment the test was executed in. Our test environments are extremely dynamic in that db schemas are refreshed frequently, new builds are installed, and various browsers are used. This information is needed for each test run for tracking and performing root causes analyses.
Some of our tests runs are quite lengthy it would be nice to know how far along an automated test run is. This could be as simple as determining the average time usuallly taken for that test run and showing where the current run is within that time as is done in Jenkins.
Linking requirements to tests is a time-consuming task - there is no quick and easy way to do it. It would be great if you could include the path/name of the requirement(s) a test should be linked to in the CSV file that is used to upload tests into QA Complete. The prerequisite would be that the requirements are loaded prior to loading the tests.
I have a product that requires testing for multiple clients and will use tokenized tests to pass different data (usernames, field names etc). Rather than creating multiple tests that contain the same steps but different token files(1 token file per client) it would be more efficient for me to have the single test set and select which token file to use.
For example, a test that requires all fields on a form to be completed. Client A could have fields 1, 2 and 3 whereas Client B could have fields A, B and C. Each client would have different validation required and/or different character limits. Currently to use the same test I would need to edit the token file and re-upload or make a copy of the test (Which would make it harder keep updated with all the different copies if something changes).
I was thinking this process could work in a similar way to attaching configurations/releases to a Test Set. The token files will be attached to the test set and will be chosen upon running said test set.
If anyone has any methods or work arounds for me, it would be great to hear them.