Feature Requests
290 results found
-
Show the PID of process in which a test is running
I whish to be able to see the PID of the currently running test when I break in it. Thus to allow to attach a performance analyzer.
1 vote -
Risk/Progress window move to toolbar (status bar) with progress bar. Add text "xxx/yyy test pass"
Risk/Progress window move to toolbar (status bar) with progress bar. Add text "xxx/yyy test pass"
Reason: unable dock this windows in right position when clip/unclip (auto hide ) dock panels.
1 vote -
Provide an option to only enable grid node when machines has no active user sessions
I'd love to make use of the latent power of all the locked desktops in my office but don't want to risk using nodes when someone is logged in.
1 vote -
1 vote
-
Remote server: Run test on all (connected) servers
I have a test which is required to be run manually to reset the environment to a initial state.
I would like the option to run the test on all servers at once. Now I have to select "run test on server X" for each server I have which is tedious.(This feature would also be good to ensure a particular test is passing on all servers).
1 vote -
Support UITestMethod in Windows Store apps
Posted in response to: forum.ncrunch.net/yafpostsm5807UITestMethod-not-recognized.aspx.
Currently NCrunch ignores test methods with UITestMethod attribute which forces the test to run on the UI thread. This is required whenever the test needs to manipulate a UI element even if it's not a UI test in itself.
1 vote -
Add ability to bottleneck ncrunch
Sometimes I have tests which are unstable on the buildserver, since the specs of the buildserver are slower. Even when I crunch the tests locally, they still never fail. (Usually frontend tests, making use of bUnit rendering)
I would find it handy to be able to crunch tests with a forced bottleneck, limiting resources, allowing me to reproduce the buildserver circumstances.
1 vote -
Allow multiple simultaneous instances with different filters
It would be great if I could get multiple risk/progress bars pointed at different categories of tests. I would like to see (for instance) one risk/progress bar for acceptance, one for integration, and one for unit tests. It would be great if these were full parallel instances - like with their own configuration and everything. For instance, having acceptance tests farmed out to servers makes a lot of sense but all my unit tests should run locally because it takes longer to farm out a batch than to run it.
0 votes -
Add "Title" field for simplified grid node management and identification
As a NCrunch user, I would like to have an easy way to identify and manage my grid node while using distributing processing window.
Currently, "server name" field is the only way to identify remote servers. With automated, disposable, DevOps-iified infrastructure, such identification is highly desiured. Out server names are random strings, such as this:
MB-{RANDOM-8-CHARS}
- MB-DMHJBDTDD
- MB-THDRFBDF
- MB-MKDHSVTD
We don't really care or have control over this while scaling grid nodes infrastructure.
It would be nice to have an additional field "Title" or "Display Title" for grid node so that we can have a human-readable name for randomly generated…
0 votes -
In Test window, Server column for grouping rows should include all servers for children (not just one of them).
In my case Server always says "(Local)" if any child test ran locally. I think this should be a comma-delimited list like Category. Next best thing would be leaving it blank.
If I'm filtering for failed tests only, the current behavior is really a bug, because all of the failing tests may have ran on one node server that isn't (local), yet the grouping row alone still says (local). So it makes scanning the server column to troubleshoot issues (in this case node server dependency config issues) confusing.
0 votes
- Don't see your idea?