vim-force.com icon indicating copy to clipboard operation
vim-force.com copied to clipboard

Test Suites

Open b-n opened this issue 9 years ago • 4 comments

Test Suites were just launched in Spring 16. Some support for them would be super helpful.

Usecase: I have a particular feature that I want to run a set of tests on to check the coverage for my feature.

It looks like the test suites are stored in new ApexTestSuite and TestSuiteMembership objects, so maybe a query to that, and a run all tests on it? I'm not sure what they'll be adding to the API to support this directly. With some luck you can just call a the ApexTestSuite as part of the tooling API for testing.

b-n avatar Feb 18 '16 21:02 b-n

And just as I post that, I read this

You can now pass ApexTestSuite IDs to the runTestsAsynchronous() SOAP call

So maybe a facility to query the nice name, and call the test. Ideally an easy way to create a Test Suite using Vim menus, etc, would be an added bonus

b-n avatar Feb 18 '16 21:02 b-n

Hello @nzchicken Good idea. Do you have any suggestions regarding vim/ui side of this ? In terms of user experience.

neowit avatar Feb 19 '16 08:02 neowit

For me, something like :ApexTestSuite <name of suite> (where name of suite is tab completable) would make sense to get to the edit menu. The edit menu I feel should be similar to the :ApexRetrieve functionality, giving a users the ability to toggle on and off tests from the suite.

In addition to this, it would be nice if ApexTest could tab complete the suites aswell. In this case, making the query to the server every time you want to tab complete could take too long, so I would say a fair compromise would be to pull down all tests with either a seperate command, or on :ApexRefreshProject.

b-n avatar Feb 22 '16 00:02 b-n

Makes sense. Thank you for the suggestions.

neowit avatar Feb 22 '16 09:02 neowit

Just doing some house keeping and cleaning up old issues I created where I didn't follow though. Thanks though!

b-n avatar Sep 06 '23 09:09 b-n