/src_docs/developers/submitting_changes.html, v125
Simple Test Cases
There are some simple test cases which Barracuda
developers sometimes find useful.
- Browser Check - make sure the
Barracuda identifies your browser correctly
- System Resources -
check memory allocation and attempt to System.gc()
-
Simple Login App test cases - various scenarios (legacy)
-
Login
Event - should take you to the Login screen.
-
Bogus
Event - try firing an invalid event (should redirect you to the
default error screen)
-
Non-HttpRequestEvent - try and bypass the request event API and
go directly to the RenderLoginScreen handler (should redirect you to
the default error screen...this is very important, because we want
to ensure that we can limit which parts of our event model the
outside world can get to...the RenderLoginScreen event handler
assumes that certain things have already happened -- validation,
authentication, etc -- people should not be able to guess their way
into parts of an app. They should be forced to go through the API
which we expose, in this case, events which extend from
HttpRequestEvent. Consequently, the ApplicationGateway will only
dispatch events that are instances of HttpRequestEvent...anything
else will be dispatched as a general HttpRequestEvent, which can
then be redirected appropriately.)
-
Attempt Login (valid user/pwd) - actually try and Login using a
valid user/pwd (if you've already logged in once, it'll skip this
screen and take you right on in to the main screen)
-
Attempt Login (invalid user) - actually try and Login using an
invalid user (clear your session before trying this)
-
Attempt Login (invalid pwd) - actually try and Login using an
invalid pwd (clear your session before trying this)
-
Attempt Login (generate an unexpected error) - try and Login
with user='santa' to illustrate Exceptional event chaining (clear
your session before trying this)
-
Try
going to the Main Screen (w/out logging in) - shouldn't work,
unless you have logged in once already
-
Clear
session information - effectively log yourself out, clearing all
session information as you go. Again won't work unless you have
already logged in...
- Polymorphic Test [1|2|3|4|5|6|7|8|9|10]
- test impact of Polymorphism on throughput (legacy)
- App Assembly Test [Ev1|Ev2|Ev3|Ev5]
- verify app assembly (legacy)
- Simple Component Model Test Cases - various component scenarios
- URL Rewriting
/ Back Button Test - verify back button disabling works
Last Modified: 2006-01-02 15:59:13 -0500 (Mon, 02 Jan 2006)