README 1.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  1. This README gives some details about Nunit tests and samples for
  2. System.Drawing classes.
  3. Following is the directory structure for the tests and samples:
  4. Test/ (all the nunit test classes go here)
  5. System.Drawing
  6. System.Drawing.Drawing2D
  7. System.Drawing.Imaging
  8. System.Drawing.Printing
  9. System.Drawing.Text
  10. Samples/ (all the samples go here)
  11. General (samples that affect more than a single area of SD)
  12. System.Drawing
  13. System.Drawing.Drawing2D
  14. System.Drawing.Imaging
  15. System.Drawing.Printing
  16. System.Drawing.Text
  17. Please note the directory structure given above is based on System.Drawing
  18. namespaces.
  19. Advice for writing System.Drawing tests/samples
  20. ===============================================
  21. Tests are Nunit test classes and follow general Nunit test guidelines. When
  22. you write a new test class, you need to add it to System.Drawing_test.dll.sources
  23. file. Please follow the alphabetical order while adding the name of your test
  24. class.
  25. Samples are independent C# programs with a Main method. Samples are supposed
  26. to solve two purposes. First, samples expose the bugs that are not captured
  27. by Nunit tests. To achieve this, it is advisable not to repeat the code in a
  28. test and a sample for any class until unless required. Second, samples help
  29. System.Drawing users in understanding System.Drawing components as well as in
  30. writing System.Drawing applications. Writing too trivial samples for well known
  31. classes might not be really helpful for the users. It is better to write a sample
  32. to solve a particular problem.