Test Report:
Please consider the test plan sent via mail or this shared link (https://docs.google.com/spreadsheets/d/1XlkqRqVceJUcoBkPnFn8I1lV0QUm3xUzcn1wJxsLZy8/edit?usp=sharing). Feedback is appreciated. Contains a manual system test config which is used to guide our own testing and the testing of users in future steps.
login:
1. each user should be able to login using username (matr#)
2. login should not work for arbitrary matr#
3. session should not work if user is not logged in
4. user should not be able to access links without login
5. user should be able to log out
6. after logout same user should be able to login again
Please consider the summary aswell. This is not shown outside of the edit option of this site.
-----------------------------------------------------------------------------
Test Report:
Login into the system (with the matrikel number) the student signals to request financial aid. This is already the first task. By requesting financial aid the student triggers a message event, which directly goes to the front desk of the office. This is the second task. It will check whether documents are missing or not. If some documents are missing an send task will be activated and the student gets an information to supply additional documents and we get after that to the second task again. Afterwards all documents have been received the office checks the students’ info. If the student is no longer active (looking up in the database), than the request will be rejected and the user gets a message. On the other hand if the student is still active the students’ income and the income of his/her parents will be checked. Only students which don't earn too much and also their parents don't earn enough, are able to get financial aid. If the student or the parents earn too much, than the request will be rejected again and the user gets a message. If the income is ok, the financial department will transfer the aid to the students bank account and last but not least the students gets a message again. The receive task will always be activated after a decision of the office is made. In the last task the student can review the decision and after that the whole process is finished.
The matrikel number and the income statements are delivered through a simple HTML form. The matrikel number must contain exactly 8 digits and the income statement also can’t contain any letters. A spring rest server is used to transfer the entered matrikel number from the form to start the process. The camunda REST build will be started after that and the response will be send to the normal REST server which is handling the rest of the process.
