[...]How to write a good test case: 5 tips to write better test cases | Making Good Software[...]…

Thanks for the observation, I haven’t acutally ever thought about it, but you have a good point, I’ll see if I can do something to make the page more printable friendly.

Unfortunately, your page is not printable. The social banner on the left hand site is still in the print.

agood test case is

1.sipmle to understand
2.user end prosepective
3.no repaet.
4.No if loops
5.excutable
6.all cover functionality
7.un necessary.

thank u boss

With a specification I would move my code at the beginning of your method into a SetUp and then put each assertion into its own “Test” method.

This in general can give me much more readable tests and I will tend to get more information when something fails (especially when multiple something fail because I don’t need to run the test n times to know that).