NUnitASP testing for asp:Login control

[HeatherBMI]

I've been searching for a way to test this control with my NUnitASP tests for awhile now and have yet to come up with anything. I have all of my tests written, but until I can get past the initial login page, all my tests fail.

Here is some of the login page code:

<asp:Login ID="Login1" runat="server" Height="134px" 
        OnAuthenticate="Login1_Authenticate" 
        OnLoginError="OnLoginError" Width="336px" CreateUserText="Create a new account" CreateUserUrl="CreateUser.aspx" DestinationPageUrl="~/Main.aspx" MembershipProvider="SqlProvider" PasswordRecoveryText="Retrieve Password" PasswordRecoveryUrl="PasswordRecovery.aspx">
        </asp:Login>

On my NUnit tests, this is the code I have written so far...

Browser.GetPage(MyPageURL);
// This is where I need to know the control tester for my login control
// in order to use it instead of CurrentWebForm for the following
TextBoxTester user = new TextBoxTester("UserName", CurrentWebForm);
TextBoxTester password = new TextBoxTester("Password", CurrentWebForm);
ButtonTester logon = new ButtonTester("LoginButton", CurrentWebForm);
 
user.Text = "validusername";
password.Text = "validpassword";
logon.Click();

I put a writeline into my unit test right after the getpage call and it was returning the correct page, but the error message given when I run the unit test is:
NUnit.Extensions.Asp.HtmlTag+ElementNotVisibleExce ption : Couldn't find 'UserName' on ' '.

Thanks,
Heather

[HeatherBMI]

For future reference if someone else runs into this problem, here was the hack solution I came up with:

In the web.config file for my main program, I commented out the line

<deny users="?"/>

just for the duration of when I want to run my unit tests. This way, when I want to release from my localhost to my server, I can just take out the comments and everything still has the security that I needed for the main page.

Also, on all of my URLs for the Browser.GetPage() calls, I made sure to set them to read to my http://localhost:port#/....aspx instead of calling to the main server.

After doing that, all of the unit tests passed. This probably isn't the best solution to the problem, but it does give you a single point of control when you want to run your unit tests, just make sure to comment out the deny users line in the config file, but don't forget to take out the commenting before releasing it back to the server!

--This was simply the solution I came up with, and I posted it here should anyone else arrive at the same problem and look for a solution--

Heather

I've been searching for a way to test this control with my NUnitASP tests for awhile now and have yet to come up with anything. I have all of my tests written, but until I can get past the initial login page, all my tests fail.

Here is some of the login page code:

<asp:Login ID="Login1" runat="server" Height="134px" 
        OnAuthenticate="Login1_Authenticate" 
        OnLoginError="OnLoginError" Width="336px" CreateUserText="Create a new account" CreateUserUrl="CreateUser.aspx" DestinationPageUrl="~/Main.aspx" MembershipProvider="SqlProvider" PasswordRecoveryText="Retrieve Password" PasswordRecoveryUrl="PasswordRecovery.aspx">
        </asp:Login>

On my NUnit tests, this is the code I have written so far...

Browser.GetPage(MyPageURL);
// This is where I need to know the control tester for my login control
// in order to use it instead of CurrentWebForm for the following
TextBoxTester user = new TextBoxTester("UserName", CurrentWebForm);
TextBoxTester password = new TextBoxTester("Password", CurrentWebForm);
ButtonTester logon = new ButtonTester("LoginButton", CurrentWebForm);
 
user.Text = "validusername";
password.Text = "validpassword";
logon.Click();

I put a writeline into my unit test right after the getpage call and it was returning the correct page, but the error message given when I run the unit test is:
NUnit.Extensions.Asp.HtmlTag+ElementNotVisibleExce ption : Couldn't find 'UserName' on ' '.

Thanks,
Heather

[wainwrightwt]

Not sure if anybody will see this, but here is a better solution...

The problem is that NUnitAsp "Tester" objects look for a control by it's HtmlID. And ASP builds control IDs by appending all parent container names with an '_'. So, the ASP.NET Login control has the following controls:

UserName
Password
LoginButton

But, the login control itself is called "Login1". So, the UserName control's htmlid would be "Login1_UserName". If you have a masterpage, webpart, or anything else, you will also need to append those names. Here is a sample of the code I am using to test one of my login controls:

Browser.GetPage(AppPath + "Default.aspx"); //AppPath previously defined
UserControlTester master = new UserControlTester("ctl00", CurrentWebForm); // master page
UserControlTester webPart = new UserControlTester("wpMgr", master); // web part manager
UserControlTester panel = new UserControlTester("gwppanLogin", webPart); // web part container
UserControlTester login = new UserControlTester("Login1", panel); // Login control
TextBoxTester txtUserName = new TextBoxTester("UserName", login);
TextBoxTester txtPassword = new TextBoxTester("Password", login);
ButtonTester btnLogin = new ButtonTester("LoginButton", login);
 
AssertVisibility(txtUserName, true);
AssertVisibility(txtPassword, true);
AssertVisibility(btnLogin, true);
 
txtUserName.Text = "username";
txtPassword.Text = "password";
btnLogin.Click();

Alternatively, you can pull up the source code, and find the full id of the control you want to grab. (ex. "ctl00_wpMgr_gwppanLogin_Login1_UserName").

[roshworld]

Hi, there everyone. Currently I have just started working on NUnit ASP. For the past two weeks I have been working on it.

The problem I am facing now is with the visibility of the controls in NUnit.

When I tried to run the test case for validator testing, i was getting an webassertionexception where unexpectedly not visible error was coming out for all the asp controls i used. I found out that all the controls were nested in ASP:Content . Can you suggest me the way to include asp:content in unit testing in NUnit.