cgiogkarakis / wipflash

Automatically exported from code.google.com/p/wipflash
0 stars 0 forks source link

Current scenario could be reproduced without touching WPF at all #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
If someone replaced all the WPF automation with hard-coded properties, the 
scenario currently used to drive the framework would still work. The example 
app should create, persist and delete domain objects, with a separate tab for 
viewing either history or current objects.

We would like tab focusing anyway.

Original issue reported on code.google.com by featheredwings@gmail.com on 14 Feb 2010 at 8:03

GoogleCodeExporter commented 8 years ago
Tech Debt - not a bug

Original comment by featheredwings@gmail.com on 15 Feb 2010 at 1:56

GoogleCodeExporter commented 8 years ago

Original comment by featheredwings@gmail.com on 23 Feb 2010 at 2:57

GoogleCodeExporter commented 8 years ago

Original comment by featheredwings@gmail.com on 25 Feb 2010 at 11:35