Custom Fields not accessible within Test Cycle Viewer
When viewing Test Cases contained within a Test Cycle - users are allowed to filter by fields (screenshot attached). The list of fields available does not include custom fields. Filtering by custom fields is only available within the "Test Case" tab.
Test Player is completely empty/does not appear
Sometime today, the test player stopped loading for everyone on my team. This means we cannot use Zephyr Scale at all for testing and we are effectively blocked. Anytime we click on a test cycle to run it, we get a blank screen, completely empty. There was an incident today that was reported fixed, but we are still unable to use the test player!Bulk editing not available within Test Cycle - Test Cases Tab
Within the "Test Cases" tab - users are permitted to Bulk Edit via the "Edit Selected Test Cases In Bulk" option within the 'More' Dropdown. However - this same option is not available when navigating to the "Test Cycle" tab and selecting a Test Cycle and navigating to the "Test Cases" Tab. In that view - I am only able to Bulk Edit specific items such as "Environment, Tester, Release Version, and Iteration". Not clear why this is so limited. It would be very helpful to have the ability to bulk edit all the other aspects of the Test Case - in the same way that we can within the "Edit Selected Test Cases In Bulk" option within the 'More' Dropdown of the 'Test Cases' tab.'Test Cases' Tab does not allowed for filtering based on parent/associated Test Cycles
For Zephyr Scale: In the 'Test Cases' tab - users are allowed to bulk edit test cases. In fact, this is the only location within Zephyr Scale that users are allowed to bulk edit test cases. However - the filtering options within the Test Case tab lack the ability to filter/pull in test cases based on their presence in particular Test Cycles. Therefore - users are unable to bulk edit Test Cases that belong to/are associated with specific Test Cycles. This capability was available in Zephyr Squad for context (filtering by 'cyclename = ') - screenshot attached from Zephyr Squad for for reference.
accessing images
Hello, How can I programmatically access an image stored on your cloud? I need to process your XML export which contains links to images. e.g. https://cloudfront.tm4j.smartbear.com/tenant/abc/project/123/xyz.png Do you have an API for this? Something like a simple get request (authorized with an api token). What I’ve tried so far, is a Get request with a cookie called ‘jwt’ set (the value is taken from the session when I log into Attlassian). But this is not long term solution. I saw a similar question here, but with no replies https://community.smartbear.com/t5/Zephyr-Scale-Questions/Is-there-API-to-download-attachments-from-test-amp-steps/m-p/260153 Thanks!
Excel Download Testing Results detailed
Hello everyone, I would like to download a test report to Excel that shows me the status of all test steps. Zephyr Scale pulls the report cleanly with approx. 12000 lines. However, when I run the Excel download, only 53 lines appear and therefore only a fraction of the report shown before. Best regards, LeoTriple Nested Call to Test Not Seeing Driver Test Case
Good Evening, I'm attempting to author a complex Manual Test Case (MTC) using Zephyr scale. I have a single MTC that is using Test data from a data set that runs another Call to Test to login with a specific account type and a specific account role. After logging in, the MTC then executes a nested Call to Test that also has Test data from a data set that is used to execute yet another Call to Test this time using Parameters. When I run my driver MTC and look at the execution, the nested call to test doesn't iterate through the test steps for each account type and account role given the data set. When I added the nested call to tests to the test execution and ran through them it worked as intended verifying for each test data value that a certain verification took place. My question: Is there a way to have a driver MTC that uses a Call to Test which then that Call to Test uses a separate Call to Test to build out the test case? I'm thinking in terms of programming how you can have a two dimensional array with [i] and [j] being separate iterators. I need to verify multiple filter options per account type and account role so that they work and need the test case steps to reflect that. I don't want to write out 90+ steps for each account type and role.
