Automatically Testing Classic ASP

Question

I've been researching automated testing of classic ASP websites to help bring my company into the late 1990's. We run an application made up of ~14K classic ASP pages, with ASP .NET slowly gaining more of a share.

We've introduced unit tests for our core .NET functionality, but I was curious: how do others handle unit testing and automated testing for classic ASP? Especially with respect to testing both back end code, and front end pages.

Thanks, tmcg

The first goal is to prevent new code changes from breaking existing functionality. Regression and the like. — tmcg, Dec 05 '11 at 20:35
Is this solved? If you have found a solution, please post it here as an answer, so it can help others. — Ricardo Souza, Jun 24 '12 at 05:54

ulluoink · Answer 1 · 2017-11-05T17:56:59.787

5

maybe this helps? asp ajaxed Creating unit tests for classic asp

generally you need to create some infrastructure (all just vbscript code) and then you are able to do the following:

<!--#include virtual="/ajaxed/class_TestFixture/testFixture.asp"-->
<%
set tf = new TestFixture
tf.allEnvs = true
tf.run()

sub test_1()
    tf.assert 1 = 1, "1 is not equal 1"
end sub

sub test_2()
    tf.assert 1 = 2, "1 is not equal 1"
end sub
%>

test_1 would be successful and test_2 would fail obviously.

you can find the source code of that asp ajaxed framework here

there you can have a look at the testFixture.asp class

edited Nov 05 '17 at 17:56

answered Dec 05 '11 at 12:33

ulluoink

2,775
2
17
22

Your link is dead and your answer is now very little help. I'll check the WaybackMachine when I can but it would be great if you could update it. – RyanfaeScotland Nov 01 '17 at 08:59
@RyanfaeScotland updated description with some text and working links – ulluoink Nov 02 '17 at 14:53
Brilliant, thanks and thanks more for the reply, I'd forgotten about this question and had meant to come back to it. If it is of help this is now the website for the project: http://www.asp-ajaxed.org/ no to use an archive (although I found this using the archive, to get to the git repo, to find the updated homepage). – RyanfaeScotland Nov 02 '17 at 15:12

score 2 · Answer 2 · answered Nov 06 '17 at 19:27

We use Selenium successfully with an array of positive and negative tests to make sure that the pages properly function, that the back-end handles issues with bad user input and that appropriate success and error messages are displayed to the user.

This doesn't provide unit testing but it does a good job of making sure our old Classic ASP code continues running smoothly.

score 1 · Answer 3 · answered Jun 20 '12 at 21:02

1

I have used Rational Functional Tester on an ASP Classic app. It was more for the end users to get a warm and fuzzy feeling when a new feature was released. But, it does work.

http://www-01.ibm.com/software/awdtools/tester/functional/

answered Jun 20 '12 at 21:02

user1319487

43
4

score 1 · Accepted Answer · answered Jun 25 '12 at 23:34

1

We ended up going with Selenium to drive the testing, but it has not made the jump from proof of concept to implementation at large. Thanks, everyone.

answered Jun 25 '12 at 23:34

tmcg

175
1
6

Automatically Testing Classic ASP

4 Answers4