Skip to content

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.

If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

23 results found

  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Testing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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:

    https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_testing_best_practices.htm

    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…

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under review  ·  1 comment  ·  Testing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Testing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base