Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am currently using NUnit and testing a class library. Up until now, I have used a list of constants at the top of the test class to hold some static test variables. Is this the best way to do this, or is there a more fluent way to handle it?
By ‘static test variables’ do you actually mean constants (whether genuine constant, immutable instances or just ones you don’t change)? I use those frequently, and just put them at the top of the test class.
If there are several related test classes, it can be handy to separate out common values into a different class though. (It could act as your base class, but I’m not terribly fond of using inheritance just to get access to things more easily. Java static imports are handy there…)