Thanks for ur replies.
I have writte the code for delete, update etc. When i run, i get results,
TestCase MembersTest->testing_insert() passed
TestCase MembersTest->testing_insertNotable() passed
TestCase MembersTest->testing_update() passed
TestCase MembersTest->testing_updateData() passed
TestCase MembersTest->testing_insertData() passed
TestCase MembersTest->test_DeleteNoid() passed
TestCase MembersTest->test_Delete() passed
TestCase MembersTest->test_EnableMemberTest() passed
TestCase MembersTest->test_EnableMemberNottrueTest() passed
What should i do next?
after i run the test, what should i do next?
Moderator: General Moderators
- Christopher
- Site Administrator
- Posts: 13596
- Joined: Wed Aug 25, 2004 7:54 pm
- Location: New York, NY, US
- Maugrim_The_Reaper
- DevNet Master
- Posts: 2704
- Joined: Tue Nov 02, 2004 5:43 am
- Location: Ireland
The test cases are independent of the class being tested - you can use your new class as you would any class. It's only when you make future changes that you should amend and rerun the tests to ensure the changes do not break your class's API.
My typical development process involves running the entire test suite (for all tested classes) on a regular basis. Assuming the test cases only require a few seconds to complete, I'll run the entire suite after any changes to any of the covered classes - this is important when classes start relating to each other and dependencies exist. It's also a good idea that if you discover a new bug, you add that the class behaviour that the bug broke to the test cases. This is regression testing - testing that prior bugs do not reoccur.
If you want specifics, layout a more detailed scenario...
My typical development process involves running the entire test suite (for all tested classes) on a regular basis. Assuming the test cases only require a few seconds to complete, I'll run the entire suite after any changes to any of the covered classes - this is important when classes start relating to each other and dependencies exist. It's also a good idea that if you discover a new bug, you add that the class behaviour that the bug broke to the test cases. This is regression testing - testing that prior bugs do not reoccur.
If you want specifics, layout a more detailed scenario...