Hi Aliya, Thanks for the detailed feedback.
Our observations are given in blue in the concerned places in the below attached mail. We would await for any further feedback from the developer's side also. Regards Srinivasan J PMP® IBM India Private Limited EGL 'D' Block - 5th Floor , Bangalore 560 071, India Phone : Work : 91-80-41775564 , Mobile: 91-9845815258 "Aliya Walji" <[EMAIL PROTECTED]> 11/02/2008 11:54 To "Developer" <[email protected]> cc Arpita Adhicary/India/[EMAIL PROTECTED], Sreenivasulu R Borra/India/[EMAIL PROTECTED], Chandi Datta/India/[EMAIL PROTECTED], Jaganathan Srinivasan/India/[EMAIL PROTECTED], "Emily Tucker" <[EMAIL PROTECTED]> Subject Test case feedback: Configuration - session timeout Hello Arpita, This is the first email regarding feedback for the test cases you have provided for the configuration project. This email will focus on feedback for the "Session timeout' functionality. For reference, I have checked in your test cases for this feature/functionality into Subversion (source control) in the following location: Mifos > Documents > QA > v1.1 QA Documents > v1.1 New Feature Test Cases > Configuration Here's a link to the location: http://tinyurl.com/yqnh53 I have taken a look at the test case document you have provided. The first thing that is worth noting is that this particular piece of configuration will not be configured in the properties file for v1.1. Unfortunately, the configuration that resided in the database was not actually used in the code in v1.0. This was a bug. The session time out value actually came from the web.xml file and it is this file that needs to be modified to change the session timeout. We decided not to move the configuration in web.xml file into a config file in v1.1. Yes. You are correct. We will change the testcases to based on web.xml. Please see this thread for more information: http://tinyurl.com/2wqccn So, your test cases will need to be modified to take this into account. Sorry that I didn't make you aware of this earlier. I had forgotten and I guess we never updated the spec on Mifos.org. It seems we never logged an item in the issue tracker to ensure that the functionality is added to the configuration files in a future release either. I will ensure that both of these things happen. The actual mechanism for configuring session timeout has not changed between v1.0 and v1.1, however I suspect it was never tested in the first place, so I think it still makes sense for you to test this fully as part of the configuration project. The other feedback I have is that we should probably cover what happens when the user's session times out, they are redirected to the log-in page, and then they log in again. I don't think this behavior is specifically spec'd out, however I believe the user should return to the place they were when their session timed out. We should test for this specifically and log bugs where this does not happen. We have tested this feature and our test case reference - TC011 of Scenario 2 of Session Time out. The system automatically logs out and once the login happens, it takes to the home page. We assumed that is the way it should work. As per your version, if it has to go back to the screen where it was left, then there is a bug. We once again test and raise in the issue tracker. Finally, I am hoping that one of the developers (Adam Monsen, who worked in this area a little bit? Someone else?) can also provide some additional feedback from the developer perspective of areas you should add/enhance to make sure we have proper test coverage of this feature. Please let me know if you have any questions about the feedback above. I will take a look at the test case document again once you've incorporated the feedback to see if there's any other changes necessary before you being testing this functionality. Thanks, Aliya
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
