Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
most testcases now run except the ones that try to getDefaultContentId by Tool signature

fixed up tests cases so they now can run fixed tearDown method

made some private declarations protected so it can be used by other test classes

Modified the "copyToolContent" to duplicate the content repository entries, using the new copy feature in the repository. Also moved the calls to the ToolContentHandler from the web layer to the service layer, to make it easier to do the copy.

  1. … 7 more files in changeset.
Modified the "leaveToolSession" and related code to allow the tool to pass the userid (which it gets from UserDTO in the shared session) rather than pass User (which the tool doesn't have).

General changes to use UserDTO from shared session and standard URL parameters.

  1. … 11 more files in changeset.
Changed authoring to use the user from the shared session, the correct url parameters and to only update the attachment records when the user clicks save.

  1. … 18 more files in changeset.
Upgraded Hibernate to 3.0

  1. … 59 more files in changeset.
Switched to shared transaction manager and JNDI toolDataSource

  1. … 8 more files in changeset.
added new case for new method retrieveNbUserBySession

added new testcase for new method getNbUserBySession

files that are not needed

All testcases will run except in TestToolContentManager and TestToolSessionManager when the supplied parameter is null and the default content id is needed. The default content id is no longer NoticeboardConstants.DEFAULT_CONTENT_ID, but it is determined by calling getDefaultToolCOntentId (in service bean) In order for it to work, in getContextConfigLocation(), need to uncomment the values and in the testApplicationContext.xml need to uncomment the toolService and learnerService property under nbService. This however, will run only if you allocate more memory to ant, otherwise it will just hang. The test cases run, however the test-report cannot be generated. I need to find a reason behind this.

Otherwise if you leave it as is and run the test, the tests will fail in some of the testcases in TestToolContentManager and TestToolSessionManager, and the error is that you get a null pointer exception, this is

because it doesnt have the toolService in order to make the call to get the default content id

Test case is added for retrieveAttachmentByFilename

testcase for retrieveAttachmentByFilename is added

added test cases for testing NoticeboardAttachment stuff

Test case for NoticeboardAttachmentDAO

added the hbm mapping, dao definition for NoticeboardAttachment

method initAttachmentData to initialise and setup test data for test cases in relation to testing NoticeboardAttachmentDAO methods and corresponding methods in the service bean

now referenced in lams common, no need to have a copy of it in project

    • -113
    • +0
    ./lamsfoundation/lams/AbstractLamsTestCase.java
DTO no longer used

*** empty log message ***

  1. … 2 more files in changeset.
testcases to test the functions calculateTotalNumberOfUsers getSessionIdsFromContent getNumberOfUsersInSession

testcase added for new function get number of users in session

new test case for new function getSessionsFromContent

testcases for testing addUser and addSession in noticeboardServicePOJO. TestToolContentManager are the new test cases for the updated code , same with ToolSessionManager

test cases for addUser and addSession

new DAO bean added

init data for user

*** empty log message ***

  1. … 3 more files in changeset.
initNbUserData() - added to initialise data for a user, used for testing purposes only