| Randar Puust 2004-07-29, 5:51 pm |
| Running into some problem with our site and ACT\WAST and we are on a
time crunch, so I'm looking for as many ideas as possible.
Software:
Content Management Server 2002
Commerce Server 2002
MSIB 2.1
ASP.Net 1.1
Windows 2003
1) It uses Forms authentication. Although the documentation says this
is not supported, it seems to login fine and traverses the
application. (Note: I've setup Integrated and Basic Authentication,
but my problem does not go away. This is just here for completeness)
2) When recording the tests, I make many changes. Text boxes, check
boxes, etc.
3) After recording the test is complete, I go back in and reverse the
changes made.
4) Run the test
5) The test passes with many hits on each page and all of them return
an status code of 200. I check through the web logs and it is hitting
the server correctly.
But if I go back in, none of the values have been changed. It is like
it is reading the pages, but not submitting the changes.
It seems to fail on any page that is a CMS\MSIB page that is opened
in edit mode. Unfortunately, that is pretty much all of our data
entry screens. Although those pages are also very
JavaScript\validation heavy, so it is hard to isolate exactly what the
root cause is. Although one page, worked and saved fine and that has
tons of JavaScript.
I've tried this with ACT, WAST and OpenSTA. All behave the same way.
Some theories that I am hoping to validate and get workarounds to:
->Neither ACT or WAST appear to support client side scripting
(http://www.dotnet247.com/247referen.../51/259740.aspx). Because
of this, the validation fails and nothing is saved since it hits the
IsValid of the submit button. Is there a way to trick it into
thinking the client side script is run?
->Both are stateless. All they do is send a series of GETs and POSTs.
One thought is that it is losing the CMS context or just not going
into edit mode. I've tried using Integrated Auth and Basic Auth, with
no difference. According to one person at MS, it should work since
the context is stored in a cookie and should re-instantiate the
context on each page.
->The ViewState that is sent is not liked by the server. Validation
fails, so when it does the IsValid check, it just does not save the
post. It seems to send the same one each time and I can't see ASP.Net
liking that. I have been sent an article
(http://msdn.microsoft.com/library/d...enethowto10.asp)
with a workaround and am starting to investigate this.
Any other possibilities?
|