Unit test issues...

Avatar
Permanently deleted user
Created

When it comes to unit tests you should:

1. Mark (gutter) tests (methods) and their setup and teardown.=20 2. Take
attributes into account (as an alternative to the TestXXX and XxxTest
convention (and SetUp and TearDown)).

3. Allow turning the ignore attribute on both methods and classes.

4. Allow rename refactoring of TestXxxx classes: I.e., if a TextXyzAbc class
exists then renaming XyzAbc to (say) XyzDef should result in renaming the
test to TestXyzDef...

Questions

1. What happens if both csUnit and Nunit are referenced in a project?

2. What about Fit -- Fit rename refactoring and code generation is so badly
needed!!!

Amir



Votes

0

Share

1 comment
Avatar
Permanently deleted user
Created

1. Mark (gutter) tests (methods) and their setup and teardown.=20


Why? This is meaningless....

2. Take attributes into account (as an alternative to the TestXXX and
XxxTest convention (and SetUp and TearDown)).


Always has this. According to the concrete test system rules.

3. Allow turning the ignore attribute on both methods and classes.


???? What do you mean?

4. Allow rename refactoring of TestXxxx classes: I.e., if a TextXyzAbc
class exists then renaming XyzAbc to (say) XyzDef should result in
renaming the test to TestXyzDef...


Please post this suggestion to the tracker

1. What happens if both csUnit and Nunit are referenced in a project?


Any random subsystem will be selected.

2. What about Fit -- Fit rename refactoring and code generation is so
badly needed!!!


What do you mean? Please clarify.

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.