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.
-
Salesfroce Automation testing
It will be great if gearset implements salesforce automation tools like Selenium, Accelq, Testim, opkey ect.
The customer will have all the tools together( deployment, data backup, and testing automation).
Salesfroce Automation testing
3 votes -
Run Flow tests during test monitoring jobs
With the new flow tests, it would be nice if we could also have these run within test monitoring jobs.
1 vote -
5 votes
-
Throw Error When Invalid Test is Entered
When entering test class names in the text field, invalid entries can be added without any indication that there is something wrong, which would lead to uncovered code and most likely a failed deployment. For example, entering in ThisIsAnInvalidTestName would not result in any error.
10 votes -
Exclude specific Classes from Scheduled Unit Tests
Some Testclasses only run successfully, when the Org is connected to a Backend Application. Usually sandboxes for Development are not connected to the Backend. These are the Orgs, that we need to watch. It would be useful to exclude specific Classes on specified Environments from being tested in scheduled Unit Tests.
4 votes -
it would be great if deployments could be done automatically based on a event trigger
To facilitate Automated Testing, it would be great if a deployment could be triggered by an event (such as a commit by a dev), so that an org is created to allow functional automated tests (not unit tests) to be run automatically without requiring any manual process
1 vote -
Provide the option to skip code coverage when running tests on a schedule
skipping code coverage on apex test execution, helps tests finish faster.
1 vote -
Add 'run selected tests' in nightly scheduled Unit Tests Jobs.
We can select which tests run in Validation. It would be great if we could do the same in a nightly monitoring job.
2 votes -
Ability to have Tests to Run during Validation to default to Unchecked all
Ability to have Tests to Run during Validation to default to Unchecked all vs all checked (even before they finish loading into the component). We often validate with only a few tests or predefined group of test classes that we input into 'Specify Tests to run' and if a user inputs those test classes in the text area before all the Tests populate above in the list, it will include all of the ones available. It defaults to checked all and they need to remember to uncheck them or to wait for them all to load which can take awhile…
3 votes -
Allow run tests not only by specific name but by regex
We have a lot of tests and it takes about 2 hours to run them all. But we also have some small services almost completely isolated and which have a specific test class name convention. Currently, we're using ant to specify which exactly we want to run on these services build, so we don't have to wait for 2 hours to deploy a small fix to an isolated service.
1 vote -
3 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 votes -
Give Permissions to Edit Automated Job Settings
Adding a feature to give users permissions to edit & delete Automated Test Jobs would be great. Today I had to hunt down a colleague to be have him edit his job when all I had to do was change the schedule. This feature would have saved a lot of time.
2 votes -
Automated User Test Suite Integration
Such as Selenium and/or Cypress.io
4 votes -
Display which apex triggers have low code coverage if a deployment fails
It would be great if Gearset can surface which Apex trigger has 0% code coverage when a deployment fails.
9 votes -
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.
10 votes -
Specify tests to run on the test monitoring jobs
Some of my orgs have many tests, and I don't always want to run all of them on a daily basis. Being able to specify which tests are run daily would be great.
7 votes -
Provide option to disable parallel apex testing in Scheduled Tests
Scheduled Test runs can fail due to UNABLETOLOCK_ROW errors. This is due to what amounts to a bug in SF: accessing public custom settings in tests which are run in parallel can cause deadlocks. Really, the tests ought to be isolated from each other, but they are not. See:
The workaround in SF is to disable parallel apex testing.
If Gearset could do that during the scheduled test run, it would prevent false test failures.
I guess I could change the option on the SF org, but sometimes parallel testing is useful, so I wouldn't want to…
7 votes -
Test job triggered by CI job
Test jobs are only configured on time basis. When developer commit some changes and it will be deployed, but tests will be done on a time basis in 2 hours for example, so he should wait to know weather tests are passed or not. Or ask the release manager to run tests manually. So, this feature is must have improvement.
1 vote -
Provide a way to get the debug logs of failing tests
Sometimes my tests are failing when they run during the automated run at night, but, when I log in and run the tests manually, they pass. I can see the failure stack trace, but I was wondering if there is any way to keep/view the debug logs from the failed tests so I can try to understand why they fail at night, but work during the day?
4 votes
- Don't see your idea?