Khurram Aziz : ASP.NET, Software Engg.

ASPX Parser

khurram — Tue, 18 Jul 2006 15:49:00 GMT

As time to market is becoming important factor; we the developers usually get very low time to make things the right way. We have to rely on frameworks, runtimes and libraries to do the heavy lifting. While designing the app in such scenarios you have...(read more)

Characteristics of Good Portal Framework

khurram — Fri, 28 Oct 2005 18:11:00 GMT

So what a good portal platform should provide you? Add new things and vote listed item on scale 0 (no need) to 10 (it will not be a portal platform if it does not have this)

User Management System
Security System
Extendable
Mobile Support
Online help/documentation of portal platform
[F] Community Support, Lots of controls/add-ons available
Compatibility/Option to host controls/add-ons of other platforms
Admin interface to setup portal
XML based configuration files for power administrators
[J] Rich Text Editor
[K] RSS Support
[L] Search Capability
[M] Import / Export
Skinning Support
Have that X control (X = Blogs, Wiki, Forums, or some of your favourite)
[P] Email Notifications / Newsletters

My opinion

A=10, B=10, C=10, D=5, E=5, F=5, G=5, H=0, I=10, J=5, K=5, L=5, M=5, N=5, O=5 / X=Wiki, P=10

NUnitASP :: Unit Testing Web Based User Interfaces

khurram — Wed, 26 Jan 2005 19:07:00 GMT

Testing is an important defect removal technique. Unit testing is the most affective regression testing technique. NUnit is the mostly used CASE tool people uses around. NUnit helps us unit test class libraries. The missing part had been non availability of similar tools for the user interface layers, especially web application due to its wide use. But not anymore, as NUnitASP is available as an extension to NUnit.

To use NUnitASP, add reference to the NUnitASP assembly, derive your unit test class from WebFormTestCase base class. Access your web application using Browser property that you will get from the base class. Get web-controls test objects by providing the ids of your web controls on the web application page. Set and fire events of these web controls using the test web-controls. Get the values of the web-controls and use WebAssertion helper class that’s shipped with NUnitASP. Use the same NUnit GUI or console interfaces to open the assembly of your unit test class and you will see the list of your ASP.NET aware unit tests.

Here is one simple “Hello World” unit test class built using NUnitASP. It unit test a web form that has three controls, Button1, Label1 and TextBox. The web form simply set the label text equals to the text box text prefixed with word, Hello on the click of the button.

[NUnit.Framework.TestFixture]

public class UnitTest : NUnit.Extensions.Asp.WebFormTestCase

{

public UnitTest() {}

[NUnit.Framework.Test]

public void HelloWorldTest()

{

string strURL = @"http://localhost/WebApplication1/WebForm1.aspx";

this.Browser.GetPage(strURL);

NUnit.Extensions.Asp.AspTester.ButtonTester Button1 = new ButtonTester("Button1", this.CurrentWebForm);

NUnit.Extensions.Asp.AspTester.LabelTester Label1 = new LabelTester("Label1", this.CurrentWebForm);

NUnit.Extensions.Asp.AspTester.TextBoxTester TextBox1 = new TextBoxTester("TextBox1", this.CurrentWebForm);

string strValue = "World";

TextBox1.Text = strValue;

Button1.Click();

strValue = "Hello " + strValue;

WebAssertion.AssertEquals(strValue, Label1.Text);

}