Re: [Fat-develop] Re: FAT Acceptance Tests
Brought to you by:
exortech
Menu
▾
▴
Re: [Fat-develop] Re: FAT Acceptance Tests
|
From: Darren M. <DMc...@th...> - 2004-01-20 20:24:01
|
hi owen , Thanks for the detailed response. 2) I've installed vs.net 2002, it's useful to have and seems to work fine alongside vs.net 2003. I haven't had any problems in vs.net 2002 or 2003 with dots in project names. Everything worked fine. I've been doing some work on WebTest today. We had some problems with submit not submitting fields that are not explicitly set by the test - We had to call Page.RepopulateFormTags() right after each post in the test. We modified Page to call this on construction and fixed some other bugs in code called by Page.RepopulateFormTags(). I'll try and get the fixes checked in. Is the strategy to get rid of PageParser.cs entirely (is it possible?), and use the dom in mshtml instead. BTW - I'm working on getting some clickable thumbnails of web test results. Darren. Owen Rogers <OR...@th...> Sent by: fat...@li... 15/01/2004 02:51 To: Darren McGrath <DMc...@th...> cc: fat...@li... Subject: [Fat-develop] Re: FAT Acceptance Tests hi darren, sorry about taking ages to get back to you on this one. i've been trying not to focus on anything else while i was getting my paper ready for XP2004. now that that's out of the way, i'm intending to do a lot more work on FAT. in answer to your questions: 1) sure. i noticed you added it but have it commented out. i think that it is important to maintain backwards compatibility until it no longer makes sense to do it. at least we want to know when we've broken it. 2) yah, i know, i know. i'm still using vs.net 2002. i just haven't bothered to upgrade. it does make things a bit of a hassle when collaborating with people on open source projects that use a different version. what we're doing on ccnet is that we have two copies of the solution and project files checked in. one for each version of vs.net. it's a bit of a hassle as we need to keep the 2 in sync, but it works well enough. 3) thanks for that. i hadn't tried running the webtest tests yet. it's good that it's in the build script now though. my intention is to rewrite this stuff test first -- probably making more use of the mshtml stuff -- now that we've sorted most of the issues with it. i need to apply the new changes that i made to webtest before leaving egg. i'll do that tomorrow. > Am I right in thinking that if we keep going down this route then FAT.Acceptance.exe will become a dll, exactly right, i've already updated it. > FAT.Console.dll will become an exe (FAT.exe!) this is only like this because vs.net doesn't allow you to reference an exe. as we need to reference FAT.exe from the FAT.Test project, i needed to keep it as a dll to keep vs.net happy. the nant file builds it as a dll though. > and AllTests.cs, FATWebTests.cs and maybe some other stuff will disappear? yup. i'll do that tomorrow too. btw, did you have any problems getting the FAT.Web project to work? i was showing it to some people here that have vs.net 2003 installed and it was complaining about the period in the project name. we removed the period and it worked, but it's a bit irksome. maybe we should rename it. any suggestions for an alternate name without the dot? cheers, o. ps. i've added syncmail, so email updates will be send out on the fat-develop list every time someone checks in changes. this means that we know when things are changing. pps. i should bug mike roberts and try to get it up on ccnetlive. --- R. Owen Rogers ThoughtWorks Ltd ThoughtWorks - Deliver with passion! |---------+----------------------------> | | Darren McGrath | | | | | | 03/01/2004 13:33 | |---------+----------------------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| | | | To: fat...@li... | | cc: Owen Rogers/Canada/ThoughtWorks@ThoughtWorks | | Subject: FAT Acceptance Tests | >--------------------------------------------------------------------------------------------------------------------------------------------------| Hi Owen, Hope all's going well in India! I've taken an initial look at FAT, done a few commits and now have a few questions ..... [1] As we're aiming at FAT being compatible with .NET Framework 1.0, would it make sense to add <property name="nant.settings.currentframework" value="net-1.0"/> to FAT.build to enforce this more explicitly? [2] I'm using VS.NET V7. The project and solution files that are checked in look like they are produced by VS.NET V6. Are you looking at moving to V7? [3] I've got all the unit tests passing in FAT.Test and FAT.WebTest (fixed the RequestCookies test by changing url to the FATWeb url from http://localpublic/pages/start.aspx which didn't exist on my machine). I've added the invocation of the FAT.WebTest.dll tests to FAT.build script. It looked like you were moving the FAT.Acceptance projects to use FAT to acceptance test itself - makes sense! I got the "Web/Run Simple Passing Test.fat" and "Console/Run Simple Passing Test.fat" acceptance tests running and passing. Am I right in thinking that if we keep going down this route then FAT.Acceptance.exe will become a dll, FAT.Console.dll will become an exe (FAT.exe!) and AllTests.cs, FATWebTests.cs and maybe some other stuff will disappear? Cheers, Darren ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Fat-develop mailing list Fat...@li... https://lists.sourceforge.net/lists/listinfo/fat-develop |
