Loading ...
Sorry, an error occurred while loading the content.

Messages List

35850

Re: TDD on UWP apps

I see a couple of ideas here: Mocking framework in UWP Apps http://stackoverflow.com/questions/33242211/mocking-framework-in-uwp-apps
jeffgrigg63132
Jan 25
#35850
 
35849

TDD on UWP apps

Hello group. I’ve been really wanting to teach my self UWP since I comfortable with WPF. Strangely enough (to some people) the biggest hurdle for me learning
immeraufdemhund
Dec 31, 2016
#35849
 
35848

Re: Long running test suite

The language can have a big impact though. I’m working in Go right now. Message passing is included in the language as channels, and there are just a few
Adam Sroka
Jun 13, 2016
#35848
 
35847

Re: Long running test suite

On Fri, Jun 10, 2016 at 6:00 PM, Kim Gräsman kim.grasman@... ... I have a colleague who tried to go that route, I agree, not pretty. But it sounds like
John Carter
Jun 13, 2016
#35847
 
35846

Re: Long running test suite

Hi John, all, ... trigger _every_ ... I've seen several test suites where people force execution order on multithreaded SUTs (using test-only synchronization
Kim Gräsman
Jun 9, 2016
#35846
 
35845

Re: Long running test suite

... parallelism to the runner. Part of me says, "Any code that depends on the exact performance of the scheduler, the load the number of CPU's, .... is flaky,
John Carter
Jun 9, 2016
#35845
 
35844

Re: Long running test suite

Hi John, I like your list of ideas, but I take a small exception with your comment about running tests on multiple threads. I agree that it sometimes
Charlie Poole
Jun 6, 2016
#35844
 
35843

Re: Long running test suite

Things I do to handle this.... * Benchmark. Every build spits out an order list of how long each test took. Attack the long ones first. * Parallelism via
John Carter
Jun 6, 2016
#35843
 
35842

Justify: support for “real” services

The soon to be released Justify Open Source project supporting rule-based CDI JUnit testing is now briefly documented for System Engineers at
y153446
Jun 5, 2016
#35842
 
35841

Re: Long running test suite

Joen, What language(s) and platform are you working with? Dave... On 22 May 2016 at 23:25, Joselito D Moreno joenmoreno@...
Dave Rooney
May 24, 2016
#35841
 
35840

Re: Long running test suite

Empty out the integration and up tests and sub in more microtests. On Mon, May 23, 2016, 12:15 'Niklas Bergkvist' niklas.bergkvist@...
Tim Ottinger
May 23, 2016
#35840
 
35839

Re: Long running test suite

Hi, I'd say you have a good opportunity for refacoring! If your tests cover your functionality; go a head and refactor into smaller functional units. good
Niklas Bergkvist
May 23, 2016
#35839
 
35838

Re: Long running test suite

http://martinfowler.com/articles/continuousIntegration.html Jump to the section: "Keep the Build Fast". -- Abraços, Josué http://twitter.com/josuesantos
Josue Barbosa dos Santos
May 23, 2016
#35838
 
35837

Re: Long running test suite

A common approach is to split your tests by type (unit, integration, UI), or at least by speed (fast, slow). Then, always run the fast tests before check-in,
Steve Smith
May 23, 2016
#35837
 
35836

Re: Long running test suite

I don't know if it still works this way, but the Flex framework used to run a dedicated nightly build for the UI tests that could take a really long time to
Avi Kessner
May 23, 2016
#35836
 
View First Topic Go to View Last Topic