Dashboard
>
WG: Programmer's Cafe
>
Sakai Programmer Manual
>
Testing
WG: Programmer's Cafe
Log In
|
Signup
Testing
Browse Space
View
I
nfo
Added by
Aaron Zeckoski
, last edited by
Aaron Zeckoski
on Jul 05, 2006 (
view change
)
Labels:
(None)
Add Labels
Enter labels to add to this page:
Tip:
Looking for a label? Just start typing.
This page is not complete, try back later -AZ
Testing in Sakai
-
Aaron Zeckoski
What is testing?
For our purposes, testing is programmatic unit testing or integration testing, this type of testing is done by the developers (not QA)
Unit testing
is used to validate that a particular module of source code is working properly
More info here:
Wikipedia - Unit test
Integration testing
is the phase of software testing in which individual software modules are combined and tested as a group to verify they work together correctly
More info here:
Wikipedia - Integration testing
Other testing like
system testing
should be done also but by QA and not by developers
How do we test in Sakai?
Logical (unit) testing is done using
JUnit
DB integration testing is done using
Spring framework
Integration testing is done using
Test Harness
Testing in Sakai
3 ways to do automated code testing in Sakai
Using Junit to do logical unit testing
More info on
Junit
[Using Spring framework to do DB integration testing]
More info about
Spring Framework testing
[Using test harness to do full integration testing]
More info at the main page:
ENC:Sakai Test Harness
Test Harness readme
Example - Enhance Task List Tool to do testing
Under construction
There are currently no attachments on this page.
Children
Hide Children
|
View in hierarchy
Testing in Sakai
(WG: Programmer's Cafe)
Site running on a free
Atlassian Confluence Open Source Project License
granted to Sakai Foundation.
Evaluate Confluence today
.
Powered by
Atlassian Confluence
, the
Enterprise Wiki
. (Version: 2.5.5 Build:#811 Jul 25, 2007) -
Bug/feature request
-
Contact Administrators