RE: [Mono-devel-list] OASIS XSLT tests converted to nunit

2005-07-11 Thread RafaelMizrahi
Ok. Agree.

rafi

-Original Message-
From: Atsushi Eno [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 11, 2005 10:46 AM
To: RafaelMizrahi
Cc: 'Andrew Skiba'; 'Oved'; 'mono-devel mailing list'
Subject: Re: [Mono-devel-list] OASIS XSLT tests converted to nunit

Hi Rafi,

It's not only for automatic test runners.

--with-test-config will still not be enough since there are several
possibile conbination of flags for manual testing. And if it forces
developers to create such possible configurations every time, or
having several configuration files, it messes developers (at least
I don't want to do that). Beauty should not precede real usability.

Atsushi Eno


RafaelMizrahi wrote:
 Atsushi,
 We strive for unity.
 We don't want to have different approaches across frameworks.
 See Ben Maurer response to Environment Variables:
 http://lists.ximian.com/pipermail/mono-devel-list/2005-June/012619.html
 
 
It should not mess testers by forcing them edit 
application config files every time
 
 
 As I know developers/testers, their first solution will be to hijack the
 file, so it's just a question of which file will they hijack? The makefile
 or the App.config file. Non of the answers is good.
 
 
 rafi
 -Original Message-
 From: Atsushi Eno [mailto:[EMAIL PROTECTED] 
 Sent: Monday, July 11, 2005 5:24 AM
 To: RafaelMizrahi
 Cc: 'Andrew Skiba'; Oved; 'mono-devel mailing list'
 Subject: Re: [Mono-devel-list] OASIS XSLT tests converted to nunit
 
 This time no. It should not mess testers by forcing them edit
 application config files every time, rather than just setting
 environment variables in their command line (including make
 command line options such as make BLAH=yes run-test).
 
 Atsushi Eno
 
 
 RafaelMizrahi wrote:
 
Andrew,
You should use ConfigurationSettings.AppSettings with an App.Config file,
instead of using Environment variables.

Vladimir already used this approach in the System.Web NUnit Test suite we
contributed to mono, which also utilizes the NUnit [Suite] attribute.

rafi
Mainsoft SDE/T 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrew
 
 Skiba
 
Sent: Wednesday, July 06, 2005 2:38 PM
To: Atsushi Enomoto
Cc: mono-devel mailing list
Subject: [Mono-devel-list] OASIS XSLT tests converted to nunit

Hi Eno.

I did what we talked about 2 days ago.

So I converted the standalone testsuite to be an NUnit [Suite]. I did 
not want to support few entry points, so I made dll instead of exe 
(exactly as in W3C xmlconf). To create reference results on dotnet I 
made a separate module, generate.cs. So to avoid code duplication, I 
took the common code from xslttest.cs and generate.cs into 
XsltTestUtils.cs. Another thing one may ask is why did I introduced all 
these env variables. The answer is - I could not parse command line 
anymore, so I made the simpliest change. More elegant way was to make 
few fixtures for every possible combination of whitespace and DOM flags, 
but I'm not sure it's worth the effort right now. Another problem with 
this idea is that generation and the testing would have different flags. 
Some more info can be found in README file (after patching it, of course).

Thank you.

Andrew.


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

 
 
 
 
 



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


[Mono-devel-list] SqlClient Tests - CS0234 errors

2005-06-27 Thread RafaelMizrahi
Hi Suresh,
I started integrating Mainsoft testing framework with mono SVN,
And when I compile the NUnit tests of System.Data I get 3 occurrences of the
error:

error CS0234: The type or namespace name 'DBNull' does not exist in the
class or namespace 'MonoTests.System.Data' (are you missing an assembly
reference?)

I have changed the 3 lines so I will be able to compile with csc.

1) Can I commit ? (be kind ;) this is my first Commit ;)
2) Or, do I have an alternative way to build this NUnit assembly using CSC ?
3) I guess that since we use the namespace convention foo1.System.foo2, this
is not the first time that CS0234 error appears.

-
Mizrahi Rafael
Mainsoft SDE/T Team Leader


SqlClientTests.patch
Description: Binary data
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

2005-06-26 Thread RafaelMizrahi
Hi Gonzalo,
Any news regards the System.Web test suite?
I will be at Out Of the Office at Microsoft TechEd for 4-8 July,
So you can ask Vladimir (has no SVN write) for any help you need.

rafi
Mainsoft SDE/T 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of RafaelMizrahi
Sent: Monday, June 20, 2005 5:03 PM
To: 'Gonzalo Paniagua Javier'
Cc: 'Vladimir Krasnov'; mono-devel-list@lists.ximian.com; 'Oved'
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

Hi Gonzalo,
Here it is ! System Web Harness integrated with NUnit and tested it on mono.

How can I send you the zip files? Since it is approximately 11MB, ximian
mail server rejects the email.

Client-side test framework
SystemWebTestSuite.zip - Web Harness integrated with NUnit 
Server-side web application
System_Web_dll.zip - 479 System.Web tests + empty System.Web tests templates
GHTWebControls.zip - web test control container 
GHTWebUtils.zip - web tests base and helper functions


TODO Roadmap:
* Transfer the files to your computer ;)
* Waiting for your review.
* Insert into SVN, and we will proceed the work from there.
I left this task to you, so you can decide where to put each component, and
how to integrate it with build and XSP.
* Mainsoft will abandon its previous harness, and will start using this
harness from the SVN.

May the 'source' be with you.
-
Mizrahi Rafael
SDE/T Team Leader
Mainsoft

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of RafaelMizrahi
Sent: Wednesday, June 15, 2005 9:49 PM
To: 'Gonzalo Paniagua Javier'
Cc: 'Vladimir Krasnov'; 'Oved'; mono-devel-list@lists.ximian.com
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

 Should we just use regular NUnit for those?
Well, I guess so.
The web testing framework targets two needs:
* Testing the rendering of web elements.
* Running tests under web context.
* Automate IE and post back. But we currently excluded this feature.

Although, it can be used for testing any class. In fact, we are using this
framework for testing other assemblies which we want to test in web context
(e.g. globalization, reflection). 

I have looked into the 479 tests and about 50 tests are non rendering
tests, for example: HttpSessionState, HttpApplicationState, but must be
tested in the context of a web application, so they cannot be used in NUnit.

So, let's agree that classes which can be used outside of ASP.NET (web
context), will be tested using NUnit tests.

rafi

-Original Message-
From: Gonzalo Paniagua Javier [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 15, 2005 7:52 PM
To: RafaelMizrahi
Cc: mono-devel-list@lists.ximian.com; Oved; Vladimir Krasnov
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

On Wed, 2005-06-15 at 17:03 +0300, RafaelMizrahi wrote:
 Hi Gonzalo,
 * We are doing some last cleanups on the web test suite and the tests base
 classes, I hope to send it (along with 479 tests! ;) for your review in
few
 days.
 * The same harness is used for two scenarios:
 * Generating expected xml files (ASP.NET on IIS). 
   Scenario is in use only once, every .NET Service Pack.
 * Getting xml files from web server (Tomcat, xsp, ...) and comparing 
   with expected xml files.
 * XHTML - We replaced the usage of SGMLReader with htmlagilitypack.
 * XMLDiff - If we wish to replace the XMLDiffPath , we can use
XMLUnit,java
 XMLDiff or in-house developed XMLDiff component.

Nice.

What about some classes such as HttpUtility that can be used from
outside of an asp.net application? Should we just use regular nunit for
those?

-Gonzalo



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

2005-06-21 Thread RafaelMizrahi
Hi gonzalo,
I have set an FTP account for mono
ftp :ftp.mainsoft.co.il
user:mono
password:'I have disclosed with you'
You can share this FTP account with more mono hackers, and use this ftp for
other large binary transactions ;) between mono and mainsoft.

The web test suite zip files are at the directory: web_test_suite (you need
all the zip files)
* Notice: files are automatically deleted after 2 weeks.

rafi

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of RafaelMizrahi
Sent: Monday, June 20, 2005 5:03 PM
To: 'Gonzalo Paniagua Javier'
Cc: 'Vladimir Krasnov'; mono-devel-list@lists.ximian.com; 'Oved'
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

Hi Gonzalo,
Here it is ! System Web Harness integrated with NUnit and tested it on mono.

How can I send you the zip files? Since it is approximately 11MB, ximian
mail server rejects the email.

Client-side test framework
SystemWebTestSuite.zip - Web Harness integrated with NUnit 
Server-side web application
System_Web_dll.zip - 479 System.Web tests + empty System.Web tests templates
GHTWebControls.zip - web test control container 
GHTWebUtils.zip - web tests base and helper functions


TODO Roadmap:
* Transfer the files to your computer ;)
* Waiting for your review.
* Insert into SVN, and we will proceed the work from there.
I left this task to you, so you can decide where to put each component, and
how to integrate it with build and XSP.
* Mainsoft will abandon its previous harness, and will start using this
harness from the SVN.

May the 'source' be with you.
-
Mizrahi Rafael
SDE/T Team Leader
Mainsoft

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of RafaelMizrahi
Sent: Wednesday, June 15, 2005 9:49 PM
To: 'Gonzalo Paniagua Javier'
Cc: 'Vladimir Krasnov'; 'Oved'; mono-devel-list@lists.ximian.com
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

 Should we just use regular NUnit for those?
Well, I guess so.
The web testing framework targets two needs:
* Testing the rendering of web elements.
* Running tests under web context.
* Automate IE and post back. But we currently excluded this feature.

Although, it can be used for testing any class. In fact, we are using this
framework for testing other assemblies which we want to test in web context
(e.g. globalization, reflection). 

I have looked into the 479 tests and about 50 tests are non rendering
tests, for example: HttpSessionState, HttpApplicationState, but must be
tested in the context of a web application, so they cannot be used in NUnit.

So, let's agree that classes which can be used outside of ASP.NET (web
context), will be tested using NUnit tests.

rafi

-Original Message-
From: Gonzalo Paniagua Javier [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 15, 2005 7:52 PM
To: RafaelMizrahi
Cc: mono-devel-list@lists.ximian.com; Oved; Vladimir Krasnov
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

On Wed, 2005-06-15 at 17:03 +0300, RafaelMizrahi wrote:
 Hi Gonzalo,
 * We are doing some last cleanups on the web test suite and the tests base
 classes, I hope to send it (along with 479 tests! ;) for your review in
few
 days.
 * The same harness is used for two scenarios:
 * Generating expected xml files (ASP.NET on IIS). 
   Scenario is in use only once, every .NET Service Pack.
 * Getting xml files from web server (Tomcat, xsp, ...) and comparing 
   with expected xml files.
 * XHTML - We replaced the usage of SGMLReader with htmlagilitypack.
 * XMLDiff - If we wish to replace the XMLDiffPath , we can use
XMLUnit,java
 XMLDiff or in-house developed XMLDiff component.

Nice.

What about some classes such as HttpUtility that can be used from
outside of an asp.net application? Should we just use regular nunit for
those?

-Gonzalo



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

2005-06-20 Thread RafaelMizrahi
Hi Gonzalo,
Here it is ! System Web Harness integrated with NUnit and tested it on mono.

How can I send you the zip files? Since it is approximately 11MB, ximian
mail server rejects the email.

Client-side test framework
SystemWebTestSuite.zip - Web Harness integrated with NUnit 
Server-side web application
System_Web_dll.zip - 479 System.Web tests + empty System.Web tests templates
GHTWebControls.zip - web test control container 
GHTWebUtils.zip - web tests base and helper functions


TODO Roadmap:
* Transfer the files to your computer ;)
* Waiting for your review.
* Insert into SVN, and we will proceed the work from there.
I left this task to you, so you can decide where to put each component, and
how to integrate it with build and XSP.
* Mainsoft will abandon its previous harness, and will start using this
harness from the SVN.

May the 'source' be with you.
-
Mizrahi Rafael
SDE/T Team Leader
Mainsoft

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of RafaelMizrahi
Sent: Wednesday, June 15, 2005 9:49 PM
To: 'Gonzalo Paniagua Javier'
Cc: 'Vladimir Krasnov'; 'Oved'; mono-devel-list@lists.ximian.com
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

 Should we just use regular NUnit for those?
Well, I guess so.
The web testing framework targets two needs:
* Testing the rendering of web elements.
* Running tests under web context.
* Automate IE and post back. But we currently excluded this feature.

Although, it can be used for testing any class. In fact, we are using this
framework for testing other assemblies which we want to test in web context
(e.g. globalization, reflection). 

I have looked into the 479 tests and about 50 tests are non rendering
tests, for example: HttpSessionState, HttpApplicationState, but must be
tested in the context of a web application, so they cannot be used in NUnit.

So, let's agree that classes which can be used outside of ASP.NET (web
context), will be tested using NUnit tests.

rafi

-Original Message-
From: Gonzalo Paniagua Javier [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 15, 2005 7:52 PM
To: RafaelMizrahi
Cc: mono-devel-list@lists.ximian.com; Oved; Vladimir Krasnov
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

On Wed, 2005-06-15 at 17:03 +0300, RafaelMizrahi wrote:
 Hi Gonzalo,
 * We are doing some last cleanups on the web test suite and the tests base
 classes, I hope to send it (along with 479 tests! ;) for your review in
few
 days.
 * The same harness is used for two scenarios:
 * Generating expected xml files (ASP.NET on IIS). 
   Scenario is in use only once, every .NET Service Pack.
 * Getting xml files from web server (Tomcat, xsp, ...) and comparing 
   with expected xml files.
 * XHTML - We replaced the usage of SGMLReader with htmlagilitypack.
 * XMLDiff - If we wish to replace the XMLDiffPath , we can use
XMLUnit,java
 XMLDiff or in-house developed XMLDiff component.

Nice.

What about some classes such as HttpUtility that can be used from
outside of an asp.net application? Should we just use regular nunit for
those?

-Gonzalo



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

2005-06-15 Thread RafaelMizrahi
Hi Gonzalo,
* We are doing some last cleanups on the web test suite and the tests base
classes, I hope to send it (along with 479 tests! ;) for your review in few
days.
* The same harness is used for two scenarios:
* Generating expected xml files (ASP.NET on IIS). 
  Scenario is in use only once, every .NET Service Pack.
* Getting xml files from web server (Tomcat, xsp, ...) and comparing 
  with expected xml files.
* XHTML - We replaced the usage of SGMLReader with htmlagilitypack.
* XMLDiff - If we wish to replace the XMLDiffPath , we can use XMLUnit,java
XMLDiff or in-house developed XMLDiff component.


Rafi
Mainsoft SDE/T 


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of RafaelMizrahi
Sent: Thursday, June 09, 2005 4:55 PM
To: [EMAIL PROTECTED]; mono-devel-list@lists.ximian.com
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

Hi Gonzalo,
Vladimir has finished the prototype of the System.Web test suite engine.
The same framework will be used to generate the expected xml (html) results
and to verify them.

We have 2 problematic components that I need your help with:

=
1. The SGMLReader XHTML component 
=
1.a. Has a serious bug which is reproducible in Mainsoft and in mono.
The bug: Only one attribute from each tag (that has more than one
attributes) processed to the output.
1.b The license does not look promising.

We need to decide on an alternative component.
I should remind that we previously used the COM version tidy (which is
just a wrapper on-top of tidy library) and it was pretty immature.

I will assign Vladimir to check the htmlagilitypack which contains no
license. Maybe we should mail the author [EMAIL PROTECTED] ?
http://blogs.msdn.com/smourier/archive/2003/06/04/8265.aspx

=
2. The XMLDiff component.
=
The Microsoft XMLDiffPath component seems to work as expected on GH and on
mono.
If we will have license (or functional) problems we can always replace it
(maybe with XMLUnit).
Any progress with Atsushi on having our own XMLDiff?


Rafi
SDE/T Team Leader

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of RafaelMizrahi
Sent: Saturday, June 04, 2005 10:30 AM
To: [EMAIL PROTECTED]; mono-devel-list@lists.ximian.com
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

Hi Gonzalo,

 Mono.WebServer
Remember that Mainsoft does not use Mono.WebServer, we use Tomcat or other
Application Server, and I prefer that we will choose components that both of
us will use.

 Don't we need a POST too
I rather postpone this to a secondary phase.

 We need to lobby Atsushi
Atsushi can own the XMLDiff/XMLAssert component.

If we want to get things started:
* Our tests already written in VB, is this a problem ?
* You can start creating the NUnit helper classes.
* I will start writing a small Expected Results Generator (xml files)
* I will do some cleanups in our web tests helper classes. So we can put
them in SVN.


Rafi

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gonzalo
Paniagua Javier
Sent: Friday, June 03, 2005 2:29 PM
To: mono-devel-list@lists.ximian.com
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

On Fri, 2005-06-03 at 12:55 +0300, RafaelMizrahi wrote:
 Hi Gonzalo,
 Using NUnit as the harness and the tests as a web application, is indeed
one
 of the options. 

Moreover, to avoid the need for running xsp externally, we could just
use Mono.WebServer.

 
 The NUnit (acting as a System.Net client), need to have the following
 components:
 
 * GET a web page (use System.NET)

Don't we need a POST too? For example, sometimes we might want to
emulate a button pressed...

 * Extract the elements which participate in the test (we used DIV with ID
 starting with a known prefix (for example TESTxxx)). You don't need the
 whole BODY.
 * XHTML in order to transform the HTML into a well formed XML. (we used
 SGMLReader) 
 * Customized Clean the XML. To remove elements which can fail the test.
For
 example, ID attributes that are generated by the server, that can be
 different on every GET.
 * XMLDiff the result with an expected result generated previously using
IIS.
 We used Microsoft XMLDiffPatch. We can evaluate the XMLUnit project,
and/or
 create some sort of XMLAssert.

We need to lobby Atsushi and get a tool similar to that one that works
with mono }:-).


-Gonzalo


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

___
Mono-devel-list mailing list
Mono-devel-list

RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

2005-06-15 Thread RafaelMizrahi
 Should we just use regular NUnit for those?
Well, I guess so.
The web testing framework targets two needs:
* Testing the rendering of web elements.
* Running tests under web context.
* Automate IE and post back. But we currently excluded this feature.

Although, it can be used for testing any class. In fact, we are using this
framework for testing other assemblies which we want to test in web context
(e.g. globalization, reflection). 

I have looked into the 479 tests and about 50 tests are non rendering
tests, for example: HttpSessionState, HttpApplicationState, but must be
tested in the context of a web application, so they cannot be used in NUnit.

So, let's agree that classes which can be used outside of ASP.NET (web
context), will be tested using NUnit tests.

rafi

-Original Message-
From: Gonzalo Paniagua Javier [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 15, 2005 7:52 PM
To: RafaelMizrahi
Cc: mono-devel-list@lists.ximian.com; Oved; Vladimir Krasnov
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

On Wed, 2005-06-15 at 17:03 +0300, RafaelMizrahi wrote:
 Hi Gonzalo,
 * We are doing some last cleanups on the web test suite and the tests base
 classes, I hope to send it (along with 479 tests! ;) for your review in
few
 days.
 * The same harness is used for two scenarios:
 * Generating expected xml files (ASP.NET on IIS). 
   Scenario is in use only once, every .NET Service Pack.
 * Getting xml files from web server (Tomcat, xsp, ...) and comparing 
   with expected xml files.
 * XHTML - We replaced the usage of SGMLReader with htmlagilitypack.
 * XMLDiff - If we wish to replace the XMLDiffPath , we can use
XMLUnit,java
 XMLDiff or in-house developed XMLDiff component.

Nice.

What about some classes such as HttpUtility that can be used from
outside of an asp.net application? Should we just use regular nunit for
those?

-Gonzalo



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] Preview of release notes.

2005-06-14 Thread RafaelMizrahi
Miguel,
The link is broken.

rafi

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Miguel de
Icaza
Sent: Tuesday, June 14, 2005 5:25 PM
To: [EMAIL PROTECTED]
Subject: [Mono-devel-list] Preview of release notes.

Here is a preview of the release notes, please send me updates before
the release:

http://www.go-mono.com/archive/1.1.8/

-- 
Miguel de Icaza [EMAIL PROTECTED]
Novell, Inc.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] Preview of release notes.

2005-06-14 Thread RafaelMizrahi
Damn IE, DNS error,
I tried on FireFox and it works fine.
Beware Microsoft, I might convert ;)

Sorry for the noise.
rafi

-Original Message-
From: Gary M. Smithrud [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 14, 2005 5:36 PM
To: mono-devel-list@lists.ximian.com
Cc: RafaelMizrahi; 'Miguel de Icaza'; [EMAIL PROTECTED]
Subject: Re: [Mono-devel-list] Preview of release notes.

I was able to get to the link fine, so there is some other issue.

On Tuesday 14 June 2005 10:30, RafaelMizrahi wrote:
 Miguel,
 The link is broken.

 rafi

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Miguel de
 Icaza
 Sent: Tuesday, June 14, 2005 5:25 PM
 To: [EMAIL PROTECTED]
 Subject: [Mono-devel-list] Preview of release notes.

 Here is a preview of the release notes, please send me updates before
 the release:

   http://www.go-mono.com/archive/1.1.8/

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] xslttest patch

2005-06-06 Thread RafaelMizrahi
I cannot find 'should', either ;)
http://www.mono-project.com/Special:Search?search=shouldfulltext=Search

rafi
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrew Skiba
Sent: Monday, June 06, 2005 9:37 AM
To: Atsushi Eno
Cc: mono-devel mailing list
Subject: Re: [Mono-devel-list] xslttest patch

Atsushi Eno wrote:
   The purpose of the patch is to make this suite as similar as
   possible to w3c suite.
 
 Please explain what it exactly means.

It accepts now the same files, like knownFailures, fixme, etc., as the 
W3C testsuite. The output is also unified with w3c. It's easier to use 
testsuites with similar input-output conventions. In addition, it fixes 
the bug with too many open files, and provides much more information 
about which testcases were fixed, which regressed, which tests took more 
time to perform, and the summary at the end, with number of testcases 
that passed, failed, regressed, etc. Again, all those things already 
present in W3C, now I added them to this testsuite, too. Just run the 
testcase before and after the patch, the difference is obvious. BTW, 
please use the patch I attached now, it fixes a typo.

 At least I will fix those messages (unless you fix by yourself)

The messages I just copied from w3c testsuite, as they are. So if you 
want to fix them, let's fix in both places.

 To understand why, I hope the link below would help you.
 
 http://www.mono-project.com/Special:Search?search=mustfulltext=Search

Do you mean that mono project never uses word must? Please, tell me 
how would you write those messages.

Regards,
Andrew.

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] System.Drawing Tests - image recognitionsimilarities

2005-06-05 Thread RafaelMizrahi
Hi Jordy,
I have a first proposal for automatic testing of System.Drawing:

1. Use W3C SVG conformance test suite test files 
http://www.w3.org/Graphics/SVG/Test

2. Use SVG# library in order to convert SVG files into a picture.
And SharpVectorGraphics (aka SVG#):
http://sourceforge.net/projects/svgdomcsharp
http://www.gotdotnet.com/workspaces/releases/viewuploads.aspx?id=8bcf7f55-ac
4f-4778-9792-37d3e69ecf5c

3. Compare the SVG image with the expected image using MSE.
ImageMagick is also using MSE for image comparison.
http://www.imagemagick.org/script/compare.php
If MSE is not fine enough, we will add more compare algorithms to the
process.

-
Mizrahi Rafael
Mainsoft SDE/T
-Original Message-
From: Jordi Mas [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 30, 2005 10:44 PM
To: RafaelMizrahi
Cc: Oren Gurfinkel; mono-devel-list@lists.ximian.com
Subject: Re: [Mono-devel-list] System.Drawing Tests - image
recognitionsimilarities

El dl 30 de 05 del 2005 a les 11:05 +0300, en/na RafaelMizrahi va
escriure:
 Hi Jordi, (and mono devs)

Hi Rafael.

 Mainsoft wish to invest some effort in testing System.Drawing.
 We wish to enhance the test suite with an image compare component which
will
 compare the difference between the expected .NET image and the mono image.

 The comparer (which we just started prototyping it) will be customized and
 produce a result according to several algorithms:
 * Prior to compare: format, size, colors, resolution
 * Color - strip boarders; compare histograms to get top colors and areas. 
 * Edge Detect - edge detection, and line generation, compare line lists.
 * Histogram to detect shapes
 * FFT (or cosine transform) of sub-regions or the whole image.
 * Tangent space Vectors
 * I appreciate your inputs?

We never devoted to much time to create a System.Drawing testing suite,
as a matter of fact that it hast just been included as part of the build
testing procedure very recently.  We appreciate any effort to enhance
the current test suite.

As Ben point out, most of drawing functions test should be validated
manually and then use the value obtained to do regression testing in the
future. I mean, we run the test manually, we make sure that we look as
Microsoft, and then we write the value down and the test use that value
in the future for regression testing. The manual part needs to be done
just once.

Since we are hacking System.Drawing a lot, regression tests have become
more important. Also we depend very heavily on libgdiplus and how future
releases of this library may break things that were testing and working
on the past.

 * Do you recommend on a curtain GPL library?

My personal preference will be to use the same license that the class
library, but you better check with Miguel.

 * Does anyone have such task in his TODO list?

Right now, we are focused on finishing Managed.System.Forms and nobody
is looking into enhancing the System.Drawing tests.

If you have any questions, feel free to write to the list or me
directly.

Thanks Rafael,

Jordi,

Note: Just as word of warning: text drawing in libgdiplus does not have
advanced I18N support. Regarding codecs, some of them do not support all
the features that Microsoft does.

-- 
Jordi Mas i Hernàndez - Mono development team - http://www.mono-project.com
Homepage and LiveJournal at http://www.softcatala.org/~jmas



___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

2005-06-04 Thread RafaelMizrahi
Hi Gonzalo,

 Mono.WebServer
Remember that Mainsoft does not use Mono.WebServer, we use Tomcat or other
Application Server, and I prefer that we will choose components that both of
us will use.

 Don't we need a POST too
I rather postpone this to a secondary phase.

 We need to lobby Atsushi
Atsushi can own the XMLDiff/XMLAssert component.

If we want to get things started:
* Our tests already written in VB, is this a problem ?
* You can start creating the NUnit helper classes.
* I will start writing a small Expected Results Generator (xml files)
* I will do some cleanups in our web tests helper classes. So we can put
them in SVN.


Rafi

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gonzalo
Paniagua Javier
Sent: Friday, June 03, 2005 2:29 PM
To: mono-devel-list@lists.ximian.com
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

On Fri, 2005-06-03 at 12:55 +0300, RafaelMizrahi wrote:
 Hi Gonzalo,
 Using NUnit as the harness and the tests as a web application, is indeed
one
 of the options. 

Moreover, to avoid the need for running xsp externally, we could just
use Mono.WebServer.

 
 The NUnit (acting as a System.Net client), need to have the following
 components:
 
 * GET a web page (use System.NET)

Don't we need a POST too? For example, sometimes we might want to
emulate a button pressed...

 * Extract the elements which participate in the test (we used DIV with ID
 starting with a known prefix (for example TESTxxx)). You don't need the
 whole BODY.
 * XHTML in order to transform the HTML into a well formed XML. (we used
 SGMLReader) 
 * Customized Clean the XML. To remove elements which can fail the test.
For
 example, ID attributes that are generated by the server, that can be
 different on every GET.
 * XMLDiff the result with an expected result generated previously using
IIS.
 We used Microsoft XMLDiffPatch. We can evaluate the XMLUnit project,
and/or
 create some sort of XMLAssert.

We need to lobby Atsushi and get a tool similar to that one that works
with mono }:-).


-Gonzalo


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


[Mono-devel-list] System.Drawing Tests - image recognition similarities

2005-05-30 Thread RafaelMizrahi
Hi Jordi, (and mono devs)
Mainsoft wish to invest some effort in testing System.Drawing.
We wish to enhance the test suite with an image compare component which will
compare the difference between the expected .NET image and the mono image. 

The comparer (which we just started prototyping it) will be customized and
produce a result according to several algorithms:
* Prior to compare: format, size, colors, resolution
* Color - strip boarders; compare histograms to get top colors and areas. 
* Edge Detect - edge detection, and line generation, compare line lists.
* Histogram to detect shapes
* FFT (or cosine transform) of sub-regions or the whole image.
* Tangent space Vectors


* I appreciate your inputs?
* Do you recommend on a curtain GPL library?
* Does anyone have such task in his TODO list?

-
Mizrahi Rafael
Dev/QA Team Leader
Mainsoft

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


RE: [Mono-devel-list] Test policy proposition

2005-05-30 Thread RafaelMizrahi
Atsushi, 
I did not suggest to convert or to run them as NUnit,
I just suggest that it is better to have their output as NUnit report.

-
Mizrahi Rafael
-Original Message-
From: Atsushi Eno [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 30, 2005 5:12 PM
To: RafaelMizrahi
Cc: 'Andrew Skiba'; 'mono-devel mailing list'
Subject: Re: [Mono-devel-list] Test policy proposition

Hi,

We will never add those massive standalone tests into NUnit test
(note that they are going to be separate module).

But it still sounds nice to develop such integration as long
as it is *optional* run.

Note that the discussion also applies to the whole standalone
test things BTW.

Atsushi Eno

RafaelMizrahi wrote:
 Hi Andrew and Atsushi,
 I suggest that all stand_alone test suites will output NUnit report.
 This way they can be included in build, regression reports etc' .

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list


[Mono-docs-list] RE: Mono-docs-list digest, Vol 1 #250 - 1 msg

2004-07-14 Thread RafaelMizrahi

Hi duncan,
I think I also alerted about a same problem at
http://lists.ximian.com/archives/public/mono-docs-list/2004-March/001011
.html

take a look at
$monodoc\class\System.Data\en\System.Data\ConstraintCollection.xml
and you can see that the member Item, appear without parameters.

MemberSignature Language=C# Value=public virtual Constraint Item {
get; }; /



--
Mizrahi Rafael
Dev/QA Team Leader
[EMAIL PROTECTED] 
Mainsoft Corporation. - Cross Platform Software Development Company
Ofek 2 Bld., North Industrial Area
Lod  71293, Israel 
Direct: (+972) 8 9781300 ext. 381 Fax: (+972) 8 9219389 
Mobile: (+972) 0507-296305
--

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, July 14, 2004 1:31 PM
To: [EMAIL PROTECTED]
Subject: Mono-docs-list digest, Vol 1 #250 - 1 msg

Send Mono-docs-list mailing list submissions to
[EMAIL PROTECTED]

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ximian.com/mailman/listinfo/mono-docs-list
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]

You can reach the person managing the list at
[EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than Re: Contents of Mono-docs-list digest...


Today's Topics:

   1. Indexer signatures in the docs. (Miguel de Icaza)

--__--__--

Message: 1
From: Miguel de Icaza [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Organization: Novell, Inc.
Date: Tue, 13 Jul 2004 22:57:42 -0400
Subject: [Mono-docs-list] Indexer signatures in the docs.

Hey Folks,

I think we have miss-generated the Item [...] signature on the docs,
for example, we show:

public Gtk.Widget Item { get; }

In Glade.XML, instead of:

public Gtk.Widget Item [string index] { get; }

This is not too bad, but we are going to do another pass at fixing
things ;-(


--__--__--

___
Mono-docs-list mailing list
[EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-docs-list


End of Mono-docs-list Digest

___
Mono-docs-list maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-docs-list