Help us improve Gearset
We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.
10 results found
-
Allow Team Members to Run Scheduled Unit Test Jobs
Execute Others’ Unit Tests
John Doe creates daily unit test job for SuperHeros R Us. He schedules it to run nightly.
Jane Smith, a member of the same Gearset team, is responsible for doing the weekly deploy for SuperHeros R Us. The unit test job from the previous day has failed (it had been previously working). Jane makes updates to the tests, and needs to re-run the unit test job. But she does not have permissions and John is out on PTO for the day. So… she needs to do it manually.14 votesReleased on December 31st, 2020
Test monitors can now be run by anyone who has validation access to the org being tested. -
List the unit tests failures in the email notification being sent out
Currently, when the unit test job fails, we can view the test history and results by going to the web page. However, we would like to view the summary of unit tests that failed in the email notification that is being sent out.
9 votes -
Support "Test Suites" for CI
Hello, Could we make a suggestion for an enhancement? For CI Unit Test jobs, could we have a Test Suite option?
4 votesYou can now specify test suites to run in CI jobs. In each CI run, Gearset will run the tests belonging to those test suites.
Feel free to drop us a message on the in-app chat with any feedback you have on running tests suites in a CI job!
Tom
-
Static code analysis - allow for exclude patterns on classes
The new static code analysis feature using PMD is a good first start but there are too many false positives to make this useful
Here is one place to start:
Allow for specification of regex patterns to exclude classes. Specifically, classes that start with xxxx_ would be most helpful as it would allow us to remove from analysis unmanaged packed code like fflib (Enterprise Patterns) or sfab (SobjectFabricator). There are hundreds of lines of PMD rule alerts from these classes
1 voteTeam owners can specify exclude patterns on the rule set configuration page.
-
Provide individual class code coverage statistics
Running tests displays overall org code coverage... it would be cool if you could provide individual class code coverage statistics as well, so we could get a good idea of what classes / triggers need attention
49 votesThis feature is now finished! Apex code coverage by class can be viewed in the details of a test job for all users with an Enterprise license.
-
Add a `Weekly` cadence to the test runner
I need to run my own tests (ie no namespace) daily as those should never fail and if they do I need to know
For namespace tests, I just need to run them weekly, primarily to reset the "invalid" flag on apex classes that can be tripped by trivial changes. I know some will fail as we have some huge apps installed and my understanding is that it's normal for dome of those managed tests to fail.
So I would only want to run them weekly to reduce the noise from the daily failure email. Just run those on Saturday.
11 votesYou can now schedule unit test jobs to run on specific days of the week, which means you can set up a weekly cadence setting the job to run on a single day.
-
"Run now" button for test automation
Adding the ability to kick off a test job on demand, rather than the daily or configurable frequency
9 votes -
CI job option "hardcore" - The deployment should fail if the static code analysis identifies errors
For CI jobs we would like to have an option that validation or deployment fails when code analysis identifies any "Error" in the Static code analysis.
4 votes -
9 votes
You can now export the results of the static code analysis as a csv file from the main deployment workflow, change monitoring results for an org and CI job runs.
-
Disable scheduled tests (temporary)
We're currently using this tool primarily for nightly unit test monitoring. However, some nights we don't want the tests to run because we'll be doing after-hours upgrades and other maintenance.
As far as we know, currently the only way to 'disable' the automatic test run is to delete/disconnect the app entirely. However this is not ideal, as we have to re-add/re-auth to turn it back on.
If Gearset had a checkbox next to each org/environment that we could enable/disable the job at will, that would be ideal.
7 votesWe’ve now released support for this. From the https://app.gearset.com/test-monitoring page you can temporarily disable test jobs and then reenable them later.
Thanks for the suggestion!
- Don't see your idea?