开云体育

Yes, sorry if I wasn't clear. the XAML and the underlying .cs file would be in the same project. But the actual Model, controllers, and other services which are pure code and don't rely on a GUI would

Hi Alan, I didn't find any such guidance last time I checked.. I wanted to create a non-trivial example but procrastinated. Caliburn looked interesting.. but no testability-oriented tutorials. Don't

:) What I meant: Windows forms was very event driven.. you keep hooking onto events exposed by objects and fill in the handlers. WPF offers no corresponding events.. it's MVVM or the

This may or may not help: http://msdn.microsoft.com/en-us/library/gg405484%28v=pandp.40%29.aspx Charlie

I have been searching a lot for some guidance and am coming up short. ?Okay, maybe an easier question: I believe that to unit test, you need to have code in a class library project rather than an

Not a clue. ?I'm presently trying to find a tutorial on TDD with Caliburn.Micro. ? Alan Baljeu ________________________________ To: testdrivendevelopment@... Sent: Tuesday, November

Nice summary. I like "mapping old experience doesn't work" ... except it's the only kind I have. :-) Charlie

Yup, me too! More recently, I've done the same using a mock view. Do you know how to do the same / similar with WPF? Charlie

I ran across this the other day... Microsoft UI Automation library "In this month's column, I will show you how to get started with UI test automation using the new Microsoft UI Automation library,

I found pex useful for teaching the concept

At present, I'm simply trying to build an understanding of good TDD with WPF. ?I'd love to find a tutorial for Caliburn.Micro that demonstrates test-driving. ?I think the prerequisite for this is to

Having difficulty visualizing what you're trying to build. Here's whats worked for me... - Use MVVM because otherwise you'd be fighting WPF most of the time.. Windows Forms and WPF are different

How do you write acceptance tests? ? Alan Baljeu ________________________________ To: testdrivendevelopment@... Sent: Tuesday, November 5, 2013 2:06:11 AM Subject: Re: [TDD] Test

In earlier times with Windows Forms I did something like this: [Test] void Test() { ? var presenter = new Presenter(); ? var view = new View(presenter); ? view.Show(); ? presenter.model.x = 3; ?

Hi, I was wondering how I would go about finding TDD's in C# for my company. Any suggestions would be greatly appreciated. Kind regards, E

There is a nice new infoq article by Henri Kniberg in which he demonstrates a simple method for testing below the UI layer http://www.infoq.com/articles/atdd-from-the-trenches

Alan, When I was last working on an app with WPF I was trying to test the GUI layer by doing things like "press button" and verifying that the presenters got events. I seem to remember that I had to

Alan, it sounds to me like you are on the right track.

Just because you can't unit test the gui doesn't mean you avoid testing the gui. You can't TDD yourself towards a good GUI. But you can write acceptance tests after the fact. When I was working on

From my (very little) experience with WPF, DataBinding is where the testing gets hard. Of course, you don't want to test that databinding works, since it's part of WPF, but there's always the risk