• starting and stopping sessions - need to add more tests (as discussed on IRC) all receive() methods - todo see ClientReceiveTest - Andy
• temporary queues - done - jeff
• durable queues. stopping and starting the server and seeing if messages are still there - done - jeff
• durable/non durable messages - done - jeff
• PagingTests - different page sizes on different destinations, global page size - clebert - done see PagingTest
• expiry queue tests - test with hierarchy and defaulting for expiry queues, i.e. i declare expiry queue A on one level of the hierarchy and override it on some sub address - done-  jeff
• dlq tests - test with hierarchy and defaulting for dlqs - done - jeff
• redelivery delay tests - see RedeliveryConsumerTest but may need more coverage
• message group tests - done see MessageGroupingTest
• browsing tests - done see ClientQueueBrowserTest
• heuristic xa tests - this is pretty easy, just commit/rollback via a management message - clebert - done see HeuristicXATest
  
• consumer tests rate limited - clebert
  
• message priorities tests - test priority on both client and server - jeff
• queue settings hierarchy - i.e. set some set of queue params at one level and make sure they're overridden proerly etc - Andy
  
• security settings hierarchy - similar to queue settings tests - Andy
  
• slow consumer tests (setting window size to zero should cause no buffering) - it can be easily tested by creating more than one consumer on the same queue, first create one consumer, then send 100 messages, then create a second consumer, and validate they're strictly round robin'd, if they're buffered they'll all be in the first consumer. - clebert... done.. see ConsumerWindowSizeTest
  
• close tests - closing session should close consumers producers etc. closing consumers should stop delivery but not consume everything in buffer
• message handler tests - setting and resetting message handler with different one - verify messages are requeued. set to null. - Andy
• sesurity - check cache gets cleared correctly, there's a config setting on configuration to control this - test security being updated on the fly
• close tests - session, consumer etc - jeff

jms tests - move any remaining non jms tests i.e. - string64klimit

• manual jms tests - remove. - done