Hi ikljaic,

First of all I'd like to thank you for your feedback and ideas for improvements - this helps us very much in building great tool for developers! And sorry for a long delay with reply - we've had lots of small things here preparing new release.

Regarding your last comment - we have lots of plans and are not going to stop working on The Welkin Suite :) There's too much great things that are missing in Salesforce development tools. We've skipped one release because of a big feature that we're going to release today - hope you'll find it helpful

Regarding improvements you've mentioned:

1. We admit that there's a huge room for improvements regarding Code Completion funcitonality. This why we are focusing on them for the next 2 sprints (4 weeks) and are going to handle situations that you've mentioned and fix lots of other issues and improve behavior as well.
2. I'm not sure that I understand what exactly you mean by this - if you're about monitoring test runs and executing new test runs - have you seen our Test Results panel (In Main Menu select View -> Test Results)? It allows you to see previous test runs with all details, run unit tests (as a regular test run or as a fake "deployment" which sometimes is faster, when SF feels bad) and rerun failed ones. If there's something missing (that you'd like or expect to have) or it's not what you've meant - please let me know :)
3. I'm not sure that we'll be able to implement regex support in Solution Explorer, but we'll try to investigate this question. As a good option I can recommend you to group files in folders in the way you'd like to.
4. We also have this in plans, but I'm not sure that we will be able to implement it before Dreamforce 15. But we'll be able to say more precise after the next 2 sprints (we have lots of refactoring around Code Completion and related analysis, so it may reduce amount of time needed to implement this feature)
5. The same as for "Go to definition". As an option we are using search in solution - not the best workaround, but at least it helps our SF devs.

Thanks once more for sharing your ideas with us and for good words. Please let us know if you have any other ideas - we are looking in details at each potential feature and improvement and often re-prioritize our backlog according to requests.

Thanks,

Vladimir

Hi ikljaic,

We have just greatly improved Code Completion functionality! You can get more details about this in our Release Notes blog post.

Thanks,

Vladimir

I've downloaded the newest version and am still playing with it. Seem great so far.

about the test triggering, ... I was having issues about the retrieval of the tests being stuck, so it looked like an incomplete feature. It takes a lot of time to start a test. Clicking to get all of the tests, waiting for them to arrive, and then running them. Unfortunately the DevConsole is in this case much faster.

Having working with the Tooling API, I understand that there is a sync and an async way of calling the webservice methods.. If you pull the definition methods in asycs periodically, you can maintain a list of the tests and execute them much faster. this would be more productive.

Rightclicking the definition of a test class, and having the context menu showing an "execute test" item (solution explorer or editor), would simplify the process much more.

Code coverage, and log inspection would be an amazing feature as well. The best part of the coverage is that it can be retrieved dynamically from a soql query, allowed only from the tooling API, which you must be using.

Hi ikljaic,

First of all I'd like to say thank you for providing detailed information about your expectations.

Have you noticed any pattern with tests being stuck? Also was it on the latest version or on the previous ones? We'll take a look what can be the issue here.

Regarding slowness of tests retrieving while starting test - we've implemented caching, thus if you haven't added any test classes you should have tests displayed to you immediately (while you still should have the option to refresh the list from org). If this doesn't work for you - please let me know (or it's anyway slow).

Also you can rerun tests directly from Test Results panel with a right-click on any test job and/or test class - if you're working with the same set of tests all the time this may speed up the process.

Btw, maybe we'll consider adding a hotkey to rerun last test job. What do you think about this - will it be helpful?

Regarding running tests from editor/solution explorer - this is an ultimate goal and we're moving towards it. Unfortunately background async calls are not ideal solution cause balance should be kept between # of API calls (to not block the org) and lag in data updates. Thus if polling interval is big enough there's a chance to confuse user providing him outdated information. Anyway - we will provide this functionality (with some ways of configuration), but I won't say when exactly it'll be implemented (worst case - couple of months).

Regarding code coverage - it's currently implemented (you can open Code Coverage panel using "View -> Code Coverage" menu). The same for logs - using "View -> Logs window" you can display logs in nearly real-time. Please let me know if both this things does not meet your expectations.

Thanks once more for sharing your opinion,

Vladimir

In my curtrent solution, I have everything retrieved. but it still takes aprox 5 min to get the results after the "run tests" button click in the test pane.

Reruning all tests or just the failed ones, is really usefull, but I was thinking more about the situation when I write a new test class, publish it to the org and run it for the first time. to run it for the first time, all of them are being retrieved and then going through the list is somewhat painful.

The code Coverage window does not return any results to me. clicking on Show coloring or refresh does not have any effect on open classes. Doing intuitive things does not return any success for me.

Did not see the logging pane yet. now I see it works well. some advanced filtering would be amazing for this. 

I was playing with this  for a while inside .Net and built some tools for myself. Most of the information can be resolved through soql queries and should be almost instant. like for instance the code coverage. if you query the "ApexCodeCoverageAggregate" object you will get a really simple way to retrieve everything you need in a matter of miliseconds. From the behaviour of the app, I believe that you might be getting stuff from SF too often on a recrd basis and not on a collection basis. not bulkifying it enough.

Hi ikljaic,

Can you please confirm that you're using 0.20.11.4 or 0.20.12.4 version so we'll check this issues?

At a high level the things that you're describing about Test Runner and Code Coverage are bugs that should be fixed.

Regarding ApexCodeCoverageAggregate - we're using exactly it as well as everything else as much as possible is bulkified (Salesforce development teaches developing everything bulkified :)).

I'll get back to you tomorrow with some more details about issues you've mentioned.

Thanks,

Vladimir

Hi

I'm using 0.20.11.4. Once it returns it in 2 seconds, then it waits for several minutes. The same behavior appeared on multiple orgs.

Also, the search pane is causin the suite to crash after changing the filtering word