Nunit test design

Question

I'm designing tests via selenium for the first time. My testing is against a web application logging in filling out data confirming and submitting etc. Is it better to have a long script (NUnit test method) with multiple asserts or console messages; Or is it better to have multiple tests each logging into the application and flowing through the same process checking and stopping at different points?

Amit Choudhary · Answer

Your question is too broad to answer. But I'll try to give you leads where you should look up. NUnit is a unit test framework and can be used for multiple test types. So you should first know the capabilities of NUnit. Read about it. Usually a tests structure goes like: public void SomeActions_Test() { // 1. Setup variables and data // 2. Take actions and collect results // 3. Place assertions against results. } No long body methods should be avoided. Try to write reusable pieces in code. E.g. If you have a test to login. Write a method that will have logic to login. Use that method in Login tests and put asserts against the returned value of that method. Use the same method call in other methods for login purpose but in this case you don't need to assert the login I mean you can if you want but this will save you a lot of duplicate code. E.g. private bool Do_Login(...parameters....) { // perform login in application. } public void Login_Test() { var result = Do_Login(... supply parameters.. ); Assert.IsTrue(result Login failed.); } public void ChangePassword_Test() { var login = Do_Login(... supply parameters.. ); // Actions to change password // Asserts goes here } Similarly you can write more reusable stuff that you see fits in multiple scenarios.

Blake · Answer

I think my main issue is that after each test the driver quits via the framework. So if i create multiple NUnit tests just checking different elements are present and that form validation is present; In between each test the browser will close and then startup again and have to log-in flow through application to assert they're present and this will take a long time running through tests. Whereas currently I have written one NUnit test which runs through application calling multiple asserts and writing to console informing me which elements are present and which errors occur. This means the application only fires up once and is a much faster test.