467,132 Members | 1,222 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,132 developers. It's quick & easy.

Reading test data for NUNIT from a file

Hey all,

I'm using NUNIT to test our classes. However, I don't want to hard
code test data into the NUNIT classes. For example, to test adding a
new Client, I don't want to hard code the Client Name, phone number,
email, etc. I want to the NUNIT to read this data from a file. This
way I can change the data in a file easily and test various types of
test data.

I think this can be done using the CONFIG file that NUNIT reads. Is
there any other way? Does NUNIT have other method of doing this?
Thanks.
TC

Jul 13 '06 #1
  • viewed: 5411
Share:
6 Replies
What about using the standard app.config file to store that information?
<tc******@yahoo.comwrote in message
news:11**********************@b28g2000cwb.googlegr oups.com...
Hey all,

I'm using NUNIT to test our classes. However, I don't want to hard
code test data into the NUNIT classes. For example, to test adding a
new Client, I don't want to hard code the Client Name, phone number,
email, etc. I want to the NUNIT to read this data from a file. This
way I can change the data in a file easily and test various types of
test data.

I think this can be done using the CONFIG file that NUNIT reads. Is
there any other way? Does NUNIT have other method of doing this?
Thanks.
TC

Jul 13 '06 #2
Just in case you were wondering *which* app.config

http://nunit.com/blogs/?p=9

Pranshu

Jul 13 '06 #3
tc******@yahoo.com <tc******@yahoo.comwrote:
I'm using NUNIT to test our classes. However, I don't want to hard
code test data into the NUNIT classes. For example, to test adding a
new Client, I don't want to hard code the Client Name, phone number,
email, etc. I want to the NUNIT to read this data from a file. This
way I can change the data in a file easily and test various types of
test data.

I think this can be done using the CONFIG file that NUNIT reads. Is
there any other way? Does NUNIT have other method of doing this?
In both Java and .NET, I prefer to bundle test data as resource files -
in .NET, this means they are compiled into the test assembly. You can
then use Assembly.GetManifestResourceSource to load the file.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Jul 13 '06 #4
Jon,
Do you have a NUNIT code example of how you would read the config file
or the resource file?
Thanks.
Jon wrote:
tc******@yahoo.com <tc******@yahoo.comwrote:
I'm using NUNIT to test our classes. However, I don't want to hard
code test data into the NUNIT classes. For example, to test adding a
new Client, I don't want to hard code the Client Name, phone number,
email, etc. I want to the NUNIT to read this data from a file. This
way I can change the data in a file easily and test various types of
test data.

I think this can be done using the CONFIG file that NUNIT reads. Is
there any other way? Does NUNIT have other method of doing this?

In both Java and .NET, I prefer to bundle test data as resource files -
in .NET, this means they are compiled into the test assembly. You can
then use Assembly.GetManifestResourceSource to load the file.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Jul 14 '06 #5
tc******@yahoo.com <tc******@yahoo.comwrote:
Do you have a NUNIT code example of how you would read the config file
or the resource file?
I'm afraid I don't have time to come up with an example at the moment -
but have you tried it? Just call Assembly.GetManifestResourceStream and
use the returned stream as you would any other stream to load data
from.

If you're having trouble, you could post a test which you'd expect to
work but doesn't.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Jul 16 '06 #6
Thus wrote Jon Skeet [C# MVP],
tc******@yahoo.com <tc******@yahoo.comwrote:
>Do you have a NUNIT code example of how you would read the config
file or the resource file?
I'm afraid I don't have time to come up with an example at the moment
- but have you tried it? Just call Assembly.GetManifestResourceStream
and use the returned stream as you would any other stream to load data
from.
May I help out :-)

I use this helper class to create and remove temporary files for unit tests.
One can use SetUp() to create a temporary file and TearDown() to remove it.

public static class TestUtility {
public static FileInfo CreateTestFile(string resourceName) {
FileInfo file = new FileInfo(Path.GetTempFileName());

Assembly assembly = Assembly.GetCallingAssembly();
Stream istream = assembly.GetManifestResourceStream(resourceName);
using(FileStream ostream = file.Open(FileMode.Create, FileAccess.Write))
{
byte[] buffer = new byte[0x2000];
int bytes;
while((bytes = istream.Read(buffer, 0, buffer.Length)) 0) {
ostream.Write(buffer, 0, bytes);
}
}

Console.WriteLine(">Created test file {0}", file.FullName);
return file;
}

public static void DeleteTestFile(FileInfo file) {
if(file != null) {
string fullName = file.FullName;
try {
file.Delete();
Console.WriteLine(">Deleted test file {0}", fullName);
}
catch(IOException ex) {
Console.WriteLine(">Cannot delete \"{0}\": {1}", fullName,
ex);
}
}
}
}

Cheers,
--
Joerg Jooss
ne********@joergjooss.de
Jul 18 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Agnes | last post: by
2 posts views Thread by d2d | last post: by
5 posts views Thread by Tom | last post: by
4 posts views Thread by geoffblanduk_nospam@yahoo.co.uk | last post: by
6 posts views Thread by Droopy | last post: by
3 posts views Thread by Anbu | last post: by
reply views Thread by angshuman.agarwal@gmail.com | last post: by
9 posts views Thread by Deckarep | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.