Test cases

QA Test Cases

Test ID	Login with	Sub-feature/Use case	Test ideas	Test type	Test data	Steps to be executed	Expected result	QA review	Dev review	PM review	Actual result	QA status	Dev status	Comments	Enviornment	OS	Browser
			Test cases
			https://digit-discuss.atlassian.net/browse/SAN-1017 https://digit-discuss.atlassian.net/browse/SAN-1159
Employee	Employee flow	Employee flow	Verify if an urban body employee is able to search without filling details. Only selecting the date range should display the results.	Functional		Login to urban local body (ULB) employee editor and go to the inbox. Click on the search application. Give the date range, from and to.	Should be able to see all the applications created in the date range and no other field should be mandatory.					Passed	Passed		UAT	Windows	Chrome
		Editor	https://digit-discuss.atlassian.net/browse/SAN-996 https://digit-discuss.atlassian.net/browse/SAN-1163
Editor	Employee flow	Employee flow	Verify application timeline, correct provider info- editor side.			Login as Citizen/Creator. Create an application and fill all details and go until last step using editor login. Validate the application timeline info.	The application timeline should show the following information: Request Completed Pending Citizen Feedback - citizen info Disposed - FSTPO (faecal sludge treatment plant operator) info Disposal in progress - Driver Info Pending for Payment - Accountant Info DSO (desludging operator) in Progress - DSO info Pending for DSO Approval - NA Pending for DSO Assignment - NA Application created - Citizen contact info.					Passed	Passed		UAT	Windows	Chrome
		DSO flow	https://digit-discuss.atlassian.net/browse/SAN-889 https://digit-discuss.atlassian.net/browse/SAN-1166
DSO	DSO flow	DSO flow	Verify if a DSO is not able to complete the request without selecting either of the choices - PREPAY- Citizen paid in cash.	Functional		Login to Citizen/Creator. Go through all the steps and create pre-pay application. Go until the DSO login. Check if a DSO is able to complete the request without selecting either of the choice.	DSO should not be able to complete the request without selecting either of the choice - PREPAY- Citizen paid in cash.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is not able to complete the request without selecting either of the choices - PREPAY- Citizen paid at counter.	Functional		Login to Citizen/Creator. Go through all the steps and create pre-pay application. Go until the DSO login Check if a DSO is able to complete the request without selecting either of the choice.	DSO should not be able to complete the request without selecting either of the choice - PREPAY- Citizen paid at counter.	Passed	UAT	WIndows		Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is not able to complete the request without selecting either of the choices - POSTPAY- Citizen paid in cash.	Functional		Login to Citizen/Creator. Go through all the steps and create pre-pay application. Go until the DSO login. Check if a DSO is able to complete the request without selecting either of the choice.	DSO should not be able to complete the request without selecting either of the choice - POSTPAY- Citizen paid in cash.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is not able to complete the request without selecting either of the choices - POSTPAY- Citizen paid at counter.	Functional		Login to Citizen/Creator. Go through all the steps and create pre-pay application. Go until the DSO login. Check if a DSO is able to complete the request without selecting either of the choice.	DSO should not be able to complete the request without selecting either of the choice - POSTPAY- Citizen paid at counter.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a Citizen receives an SMS after - PREPAY - completed request from DSO.	Functional		Login to Citizen/Creator. Go through all the steps and create pre-pay application. Go until the DSO login. Check if a DSO is able to complete the request without selecting either of the choice. Citizen receives an SMS after - PREPAY - completed request from DSO.	Citizen receives SMS after - PREPAY - completed request from the DSO.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a Citizen receives an SMS after - POSTPAY - completed request from DSO.	Functional		Login to Citizen/Creator. Go through all the steps and create pre-pay application. Go until the DSO login. Check if a DSO is able to complete the request without selecting either of the choice. Citizen receives SMS after - POSTPAY - completed request from DSO.	Citizen receives SMS after - POSTPAY- completed request from the DSO.					Passed	Passed		UAT	Windows	Chrome
		Editor	https://digit-discuss.atlassian.net/browse/SAN-890 https://digit-discuss.atlassian.net/browse/SAN-1167
Editor	Editor flow	Editor flow	Verify if an Editor is not able to complete the request without selecting either of the choices - PREPAY- Citizen paid in cash.	Functional		Login to Citizen/Creator. Go through all the steps and create pre-pay application. Go until the Editor login. Check if the editor is able to complete the request without selecting either of the choices.	Editor should not be able to complete the request without selecting either of the choice - PREPAY- Citizen paid in cash.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if an Editor is not able to complete the request without selecting either of the choices - PREPAY- Citizen paid at counter.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until the editor login. Check if the editor is able to complete the request without selecting either of the choices.	Editor should not be able to complete the request without selecting either of the choice - PREPAY- Citizen paid at counter.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if an Editor is not be able to complete the request without selecting either of the choices - POSTPAY- Citizen paid in cash.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until the editor login. Check if the editor is able to complete the request without selecting either of the choices.	Editor should not be able to complete the request without selecting either of the choices - POSTPAY- Citizen paid in cash.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if an Editor is not be able to complete the request without selecting either of the choices - POSTPAY- Citizen paid at counter.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until the editor login. Check if the editor is able to complete the request without selecting either of the choices.	Editor should not be able to complete the request without selecting either of the choices - POSTPAY- Citizen paid at counter.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if a Citizen receives an SMS after - PREPAY - completed request from Editor.	Functional		Login to Citizen/Creator. Go through all the steps and create pre-pay application. Go until the Editor login. Check if the editor is able to complete the request without selecting either of the choices. Citizen receives SMS after - PREPAY - completed request from Editor.	Citizen receives SMS after - PREPAY - completed request from Editor.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if a Citizen receives an SMS after - POSTPAY - completed request from Editor.	Functional		Login to Citizen/Creator. Go through all the steps and create a pre-pay application. Go until the Editor login. Check if the editor is able to complete the request without selecting either of the choices. Citizen receives an SMS after - POSTPAY - completed request from Editor.	Citizen receives SMS after - POSTPAY- completed request from Editor.					Passed	Passed		UAT	Windows	Chrome
		Editor	https://digit-discuss.atlassian.net/browse/SAN-978 https://digit-discuss.atlassian.net/browse/SAN-1168
UI_UX			Verify UI UX enhancements in citizen and employee logins.	Functional		Login as a Citizen/Employee. Validate the following UI UX enhancements: In Employee Login, FSM Icon in Card is missing on left top card In Update Application success screen, Localisation of Select DSO Now, Select DSO need to be changed In Update and Schedule screen from employee side, When Septic tank with soak pit is selected, needs to remove spacing in pit dimension In Collector Login, when collecting payment need to remove spacing in payment mode in radio button.	The following UI UX enhancements are validated In Employee Login, FSM Icon in Card is missing on left top card In Update Application success screen, Localisation of Select DSO Now, Select DSO need to be changed In Update and Schedule screen from employee side, When Septic tank with soak pit is selected, needs to remove spacing in pit dimension In Collector Login, when collecting payment need to remove spacing in payment mode in radio button.								UAT	Windows	Chrome
		DSO flow	https://digit-discuss.atlassian.net/browse/SAN-1024 https://digit-discuss.atlassian.net/browse/SAN-1161
DSO	DSO flow	DSO flow	Verify if a DSO is able to assign the same vehicle for multiple requests - ENGLISH.			Login as DSO. Click on inbox. Click on the application number. Click on take action and assign the vehicle. Select another application. Click on take action and assign same vehicle.	DSO should be able to assign the same vehicle to multiple requests.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is able to assign the same vehicle for multiple requests - HINDI.			Login as DSO. Click on inbox. Click on application number. Click on take action and assign the vehicle. Select another application. Click on take action and assign the same vehicle.	DSO should be able to assign the same vehicle to multiple requests.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if the vehicle capacity field and the number of trips are disabled while assigning a vehicle - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Check vehicle capacity and number of trips fields.	Vehicle capacity and number of trips should be disabled.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if the vehicle capacity field and the number of trips are disabled while assigning the vehicle - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Check the vehicle capacity and the number of trips fields.	Vehicle capacity and number of trips should be disabled.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO-assigned vehicle is captured on the new application - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Check the application.	DSO-assigned vehicle number should be captured on the new application.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO-assigned vehicle is captured on the new application - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Check the application.	DSO-assigned vehicle number should be captured on the new application.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is able to overwrite the number of trips while scheduling a vehicle - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and overwrite the number of trips.	DSO should be able to overwrite the number of trips.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is able to overwrite the number of trips while scheduling a vehicle - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and overwrite the number of trips.	DSO should be able to overwrite the number of trips.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is able to select a valid date in desludging on field - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and select the valid date.	DSO should be able to select the valid date.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is able to select a valid date in desludging on field - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and select the valid date.	DSO should be able to select the valid date.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is able to schedule a vehicle - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and click on schedule.	DSO should be able to schedule the vehicle.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is able to schedule a vehicle - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and click on schedule.	DSO should be able to schedule the vehicle.					Passed	Passed		UAT	Windows	Chrome
		FSTPO	https://digit-discuss.atlassian.net/browse/SAN-1063 https://digit-discuss.atlassian.net/browse/SAN-1157
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the home button.	Functional		Login as FSTPO on mobile. Click on the home button.	FSTPO should be able to see the home page details.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the inbox button in the FSTPO operations page.			Login as FSTPO on desktop. Click on the home button. Click on the inbox button.	FSTPO should be able to view the inbox page.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to enter all fields. The FSTPO should be able to select the application number or the vehicle log number.			Login as FSTPO on desktop. Click on the home button. Click on the inbox button. Enter all the fields or click on the application number or the vehicle log number.	FSTPO should be able to view the vehicle the scheduling page.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the search button.	Functional		Login as FSTPO on mobile. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on select. Enter the application number or the vehicle number or the DSO name.	FSTPO should be able to view the application details after being filtered.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the sort button.			Login as FSTPO on mobile. Click on the home button. Click on the add new button. Enter the vehicle number. Click on next. Click on select. Click on date (latest first or latest last).	FSTPO should be able to view the application details after being filtered.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to enter all fields and vehicle in-time and vehicle out-time in the vehicle entry log page. Also verify if the FSTPO can choose the file from the device and upload it.			Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Click on select. Fill the details in all the fields. Click on choose file, select a photo and upload it.	FSTPO should be able to enter all the fields and view photo uploaded details.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the take action button in the vehicle scheduling page.	Functional		Login as FSTPO on desktop. Click on the home button. Click on the add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button.	FSTPO should be able to view the submit button or the decline vehicle button.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO can select the submit button in the vehicle scheduling page.	Functional		Login as FSTPO on desktop. Click on the home button. Click on the add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button. Click on submit.	FSTPO should be able to view the vehicle submitted successfully message on the screen.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the decline vehicle button in the vehicle scheduling page.			Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on take action button. Click on submit. Click on decline vehicle.	FSTPO should be able to view the reason for declining.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the reason for declining dropdown.			Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button. Click on decline vehicle. Select a reason from the reason for declining dropdown.	FSTPO should be able to select any one reason.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the decline vehicle button.			Login as FSTPO on desktop. Click on the home button. Click on the add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button. Click on decline vehicle. Select a reason from the reason for declining dropdown. Click on decline vehicle button.	FSTPO should be able to view the updated successfully message on the screen.					Passed	Passed		UAT	Windows	Chrome
		FSTPO	https://digit-discuss.atlassian.net/browse/SAN-1064 https://digit-discuss.atlassian.net/browse/SAN-1158
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the home button.	Functional		Login as FSTPO on mobile. Click on the home button.	FSTPO should be able to see the home page details.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the inbox button in the FSTPO operations page.			Login as FSTPO on desktop. Click on the home button. Click on the inbox button.	FSTPO should be able to view the inbox page.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to enter all the fields. FSTPO should also be able to select the application number or the vehicle log number.			Login as FSTPO on desktop. Click on the home button. Click on the inbox button. Enter all the fields or click on the application number or the vehicle log number.	FSTPO should be able to view the vehicle scheduling page.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to enter all fields and the vehicle in-time and out-time in the vehicle entry log page. FSTPO should also be able to choose the file from the device and upload it.			Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Click on select. Fill the details in all the fields. Click on choose file, select a photo and upload it.	FSTPO should be able to enter all the fields and view photo uploaded details.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the take action button in the vehicle scheduling page.	Functional		Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button.	FSTPO should be able to view the submit button or the decline vehicle button.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the submit button in the vehicle scheduling page.	Functional		Login as FSTPO on desktop. Click on the home button. Click on the add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button.	FSTPO should be able to view the vehicle submitted successfully message on screen.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the decline vehicle button in the vehicle scheduling page.			Login as FSTPO on desktop. Click on the home button. Click on the add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button. Click on submit. Click on decline vehicle.	FSTPO should be able to view the reason for declining vehicle.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the reason for declining dropdown.			Login as FSTPO on desktop. Click on the home button. Click on the add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button. Click on decline vehicle. Select a reason from the reason for declining dropdown.	FSTPO should be able to select any one reason.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the decline vehicle button.			Login as FSTPO on desktop. Click on home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on the take action button. Click on decline vehicle. Select a reason from the reason for declining dropdown. Click on the decline vehicle button.	FSTPO should be able to view the updated successfully message on screen.					Passed	Passed		UAT	Windows	Chrome
		DSO	https://digit-discuss.atlassian.net/browse/SAN-987 https://digit-discuss.atlassian.net/browse/SAN-1165
Editor	Editor flow	Editor flow	Verify if an Editor can view the photo uploaded by a DSO.	Functional		Login to citizen/creator. Go through all the steps and create a pre-pay application/post-pay application. Go until DSO login. Login as DSO, and upload the photo.	Photo should be uploaded.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if an Editor can view the photo uploaded by a DSO.	Functional		Login to citizen/creator. Go through all the steps and create a pre-pay application/post-pay application. Go until DSO login. Login as DSO, and upload the photo. Login as editor and check if you can view the photos uploaded by the DSO.	Editor should able to view the photo in the timeline.					Passed	Passed		UAT	Windows	Chrome
			https://digit-discuss.atlassian.net/browse/SAN-1037 https://digit-discuss.atlassian.net/browse/SAN-1162
			To check if all the application timelines are aligned with the roles.			Go until the application updated/payment/ trips screen.	Application timeline should be aligned with the roles.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	To check photos uploaded by a DSO.			Login as editor, and check who has uploaded the photos.	Editor should be able to view the photo uploaded by the DSO.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To check the breadcrumbs in all the FSTPO pages.			Login as FSTPO, and check all the breadcrumbs.	Breadcrumbs should be in the format: home/Inbox/vehicle log.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To check the disposing time schedule in the AM/PM format.			Login as FSTPO, and check whether the disposal time schedule is in the AM/PM format.	FSTPO should be able to select AM/PM in the disposal scheduling page.					Passed	Passed		UAT	Windows	Chrome
			https://digit-discuss.atlassian.net/browse/SAN-1075 https://digit-discuss.atlassian.net/browse/SAN-1160
UI_UX			Verify UI UX enhancements in citizen and employee logins.			Login as a citizen/employee. Validate below UI UX enhancements. Login as citizen. In service request text change in trip number screen in create application. Login as citizen. In trip number screen in citizen side, the number of trips will be on top and vehicle capacity will be at the bottom. Login as DSO. Localisation should be changed from scheduled to update trips. Login as citizen. All location and pit details should be combined under property details.	In UI UX audit: In service request text change in trip number screen in create application should be created. Citizen should be viewable in trip number screen on the citizen side. The number of trips will be on top and vehicle capacity will be at the bottom. Schedule localisation should be changed to update trips. All the location details and pit details should be under property details.					Passed	Passed		UAT	Windows	Chrome
			https://digit-discuss.atlassian.net/browse/SAN-848 https://digit-discuss.atlassian.net/browse/SAN-1169

UAT Regression Test Cases

UAT

Test ID	Login with	Sub-feature/Use case	Test ideas	Test type	Test data	Steps to be executed	Expected result	UAT review	Dev review	PM review	Actual result	UAT status	Dev status	Comments	Environment	OS	Browser
			Test cases
			https://digit-discuss.atlassian.net/browse/SAN-1017 https://digit-discuss.atlassian.net/browse/SAN-1159
Employee	Employee flow	Employee flow	Verify if an urban body employee is able to search without filling details. Only selecting the date range should display the results.	Functional		Login to ULB employee editor and go to the inbox. Click on search application. Give the date range - from and to.	Should be able to see all applications created in the date range and no other field should be mandatory.					Passed	Passed	UAT	Windows	Chrome
		Editor	https://digit-discuss.atlassian.net/browse/SAN-996 https://digit-discuss.atlassian.net/browse/SAN-1163
Editor	Employee flow	Employee flow	Verify if the application timeline is correct Provider Info- Editor side.			Login to ULB employee editor and go to the inbox. Click on the search application. Give the date range - from and to.	Should be able to see all applications created in the date range and no other field should be mandatory.					Passed	Passed		UAT	Windows	Chrome
		DSO flow	https://digit-discuss.atlassian.net/browse/SAN-889 https://digit-discuss.atlassian.net/browse/SAN-1166
DSO	DSO flow	DSO flow	Verify if a DSO is not able to complete the request without selecting either: PREPAY- Citizen paid in cash.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until DSO login. Check if DSO is able to complete the request without selecting either of the choices.	DSO should not be able to complete the request without selecting either: PREPAY- Citizen paid in cash.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is not able to complete the request without selecting either: PREPAY- Citizen paid at counter.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until DSO login. Check if DSO is able to complete the request without selecting either of the choices.	DSO should not be able to complete the request without selecting either: PREPAY- Citizen paid at counter.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is not able to complete the request without selecting either: POSTPAY- Citizen paid in cash.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until DSO login. Check if DSO is able to complete the request without selecting either of the choices.	DSO should not be able to complete the request without selecting either: POSTPAY- Citizen paid in cash.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a DSO is not able to complete the request without selecting either: POSTPAY- Citizen paid at counter.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until DSO login. Check if DSO is able to complete the request without selecting either of the choices.	DSO should not be able to complete the request without selecting either: POSTPAY- Citizen paid at counter.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a Citizen receives an SMS after - PREPAY - completed request from DSO.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until DSO login. Check if DSO is able to complete the request without selecting either of the choices. Citizen receives SMS after - PREPAY - completed request from DSO.	Citizen receives SMS after - PREPAY - completed request from DSO.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if a Citizen receives an SMS after - POSTPAY - completed request from DSO.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until DSO login. Check if DSO is able to complete the request without selecting either of the choices. Citizen receives SMS after - POSTPAY - completed request from DSO.	Citizen receives SMS after - POSTPAY- completed request from DSO.					Passed	Passed		UAT	Windows	Chrome
		Editor	ttps://digit-discuss.atlassian.net/browse/SAN-890 https://digit-discuss.atlassian.net/browse/SAN-1167
Editor	Editor flow	Editor flow	Verify if an Editor is not able to complete the request without selecting either: PREPAY- Citizen paid in cash.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until Editor login. Check if Editor is able to complete the request without selecting either of the choices.	Editor should not be able to complete the request without selecting either: PREPAY- Citizen paid in cash.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if an Editor is not able to complete the request without selecting either: PREPAY- Citizen paid at counter.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until Editor login. Check if Editor is able to complete the request without selecting either of the choices.	Editor should not be able to complete the request without selecting either: PREPAY- Citizen paid at counter.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if an Editor is not able to complete the request without selecting either: POSTPAY- Citizen paid in cash.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until Editor login. Check if Editor is able to complete the request without selecting either of the choices.	Editor should not be able to complete the request without selecting either: POSTPAY- Citizen paid in cash.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if an Editor is not be able to complete the request without selecting either: POSTPAY- Citizen paid at counter.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay application. Go until Editor login. Check if Editor is able to complete the request without selecting either of the choices.	Editor should not be able to complete the request without selecting either: POSTPAY- Citizen paid at counter.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if a Citizen receives an SMS after - PREPAY - completed request from Editor.	Functional		Login to citizen/creator. Go through all the steps and create pre pay application. Go until Editor login. Check if Editor is able to complete the request without selecting either of the choices. Citizen receives SMS after - PREPAY - completed request from Editor.	Citizen receives SMS after - POSTPAY- completed request from Editor.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if a Citizen receives an SMS after - POSTPAY - completed request from Editor.	Functional		Login to citizen/creator. Go through all the steps and create a pre-pay application. Go until Editor login. Check if Editor is able to complete the request without selecting either of the choices. Citizen receives SMS after - POSTPAY - completed request from Editor.	Citizen receives SMS after - PREPAY - completed request from Editor.					Passed	Passed		UAT	Windows	Chrome
		Editor	https://digit-discuss.atlassian.net/browse/SAN-978 https://digit-discuss.atlassian.net/browse/SAN-1168
UI_UX			Verify UI UX enhancements in citizen and employee logins.	Functional		Login as citizen/employee. Validate below UI UX enhancements: In Employee Login, FSM Icon in Card is missing on left top card. In Update Application success screen, Localisation of Select DSO Now, Select DSO needs to be changed. In Update and Schedule screen from employee side, when Septic tank with soak pit is selected, spacing in pit dimension needs to be removed. In Collector Login, when collecting the payment, spacing in payment mode in radio button needs to be removed.	The following UI UX enhancements are validated: In Employee Login, FSM Icon in Card is missing on left top card. In Update Application success screen, Localisation of Select DSO Now, Select DSO need to be changed. In Update and Schedule screen from employee side, when septic tank with soak pit is selected, spacing in pit dimension needs to be removed. In Collector Login, when collecting the payment, spacing in payment mode in radio button needs to be removed.								UAT	Windows	Chrome
		DSO flow	https://digit-discuss.atlassian.net/browse/SAN-1024 https://digit-discuss.atlassian.net/browse/SAN-1161
DSO	DSO flow	DSO flow	Verify if DSO is able to assign the same vehicle for multiple requests - ENGLISH.			Login as DSO. Click on inbox. Click on the application number. Click on take action and assign the vehicle. Select another application. Click on take action and Assign same vehicle.	DSO should be able to assign the same vehicle to multiple requests.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO is able to assign the same vehicle for multiple requests - HINDI.			Login as DSO. Click on inbox. Click on the application number. Click on take action and assign the vehicle. Select another application. Click on take action and assign same vehicle.	DSO should be able to assign the same vehicle to multiple requests.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if the vehicle capacity, field and number of trips are disabled while assigning the vehicle - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Check vehicle capacity and number of trips fields.	Vehicle capacity and number of trips should be disabled.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if the vehicle capacity, field and number of trips are disabled while assigning the vehicle - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Check vehicle capacity and number of trips fields.	Vehicle capacity and number of trips should be disabled.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO assigned vehicle is captured on the new application - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign vehicle. Check the application.	DSO assigned vehicle number should be captured on the new application.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO assigned vehicle is captured on the new application - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign vehicle. Check the application.	DSO assigned vehicle number should be captured on the new application.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO is able to overwrite the number of trips while scheduling a vehicle - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and overwrite the number of trips.	DSO should be able to overwrite the number of trips.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO is able to overwrite the number of trips while scheduling a vehicle - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and overwrite the number of trips.	DSO should be able to overwrite the number of trips.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO is able to select a valid date for desludging on field - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and select the valid date.	DSO should be able to select the valid date.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO is able to select a valid date for desludging on field - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and select the valid date.	DSO should be able to select the valid date.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO is able to schedule a vehicle - ENGLISH.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and click on schedule.	DSO should be able to schedule the vehicle.					Passed	Passed		UAT	Windows	Chrome
DSO	DSO flow	DSO flow	Verify if DSO is able to schedule a vehicle - HINDI.			Login as DSO. Click on inbox. Click on the application number and assign the vehicle. Click on take action and click on schedule.	DSO should be able to schedule the vehicle.					Passed	Passed		UAT	Windows	Chrome
		FSTPO	https://digit-discuss.atlassian.net/browse/SAN-1063 https://digit-discuss.atlassian.net/browse/SAN-1157
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the home button.	Functional		Login as FSTPO on mobile. Click on the home button.	FSTPO should be able to see the home page details.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the inbox button in the FSTPO operations page.			Login as FSTPO on desktop. Click on the home button. Click on the inbox button.	FSTPO should be able to view the inbox page.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to enter all fields. The FSTPO should also be able to select the application number or the vehicle log number.			Login as FSTPO on desktop. Click on the home button. Click on the inbox button. Enter all the fields or click on the Application number or Vehicle log number.	FSTPO should be able to view the vehicle scheduling page.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the search button.	Functional		Login as FSTPO on mobile. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on select. Enter the application number or the vehicle number or DSO name.	FSTPO should be able to view the application details after its filtered.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the sort button.			Login as FSTPO on mobile. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on select. Click on date (latest first) or click on date (latest last).	FSTPO should be able to view the application details after its filtered.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to enter all fields and vehicle in-time and out-time in the vehicle entry log page. The FSTPO should also be able to choose the file from the device and upload it.			Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Click on select. Fill the details in all the fields. Click on choose file, select a photo and upload it.	FSTPO should able to enter all the fields and view the photo uploaded details.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the the FSTPO is able to select take action button in the vehicle scheduling page.	Functional		Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen nam. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on take action button.	FSTPO should be able to view submit button or decline vehicle button.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the submit button in the vehicle scheduling page.	Functional		Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on take action button. Click on submit.	FSTPO should be able to view the vehicle submitted successfully message on screen.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the decline vehicle button in the vehicle scheduling page.			Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on take action button. Click on submit. Click on decline vehicle.	FSTPO should be able to view the reason for declining.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the reason for declining dropdown.			Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on take action button. Click on decline vehicle. Select a reason from the reason for declining dropdown.	FSTPO should be able to select any one reason.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the decline vehicle button.			Login as FSTPO in desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on take action button. Click on decline vehicle. Select a reason from the reason for declining dropdown. Click on decline vehicle button.	FSTPO should be able to view the updated successfully message on screen.					Passed	Passed		UAT	Windows	Chrome
		FSTPO	https://digit-discuss.atlassian.net/browse/SAN-1064 https://digit-discuss.atlassian.net/browse/SAN-1158
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to select the inbox button in the FSTPO operations page.			Login as FSTPO on desktop. Click on the home button. Click on the inbox button.	FSTPO should be able to view the inbox page.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to enter all the fields. The FSTPO should also be able to select the application number or the vehicle log number.			Login as FSTPO on desktop. Click on the home button. Click on the inbox button. Enter all the fields or click on application number or vehicle log number.	FSTPO should be able to view the vehicle scheduling page.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if the FSTPO is able to enter all fields, vehicle in-time and out-time in the vehicle entry log page. THE FSTPO should also be able to choose the file from the device and upload it.			Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter vehicle number. Click on next. Click on citizen name. Click on select. Fill the details in all the fields. Click on choose file, select a photo and upload it.	FSTPO should able to enter all the fields, and view photo uploaded details.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if THE FSTPO is able to select THE take action button in the vehicle scheduling page.	Functional		Login as FSTPO in desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it . Click on take action button.	FSTPO should be able to view submit button or decline vehicle button.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To verify if THE FSTPO is able to select THE submit button in the vehicle scheduling page.	Functional		Login as FSTPO on desktop. Click on the home button. Click on add new button. Enter the vehicle number. Click on next. Click on citizen name. Fill the details in all the fields. Click on choose file, select a photo and upload it. Click on take action button. Click on submit.	FSTPO should be able to view the vehicle submitted successfully message on screen.					Passed	Passed		UAT	Windows	Chrome
		DSO	https://digit-discuss.atlassian.net/browse/SAN-987 https://digit-discuss.atlassian.net/browse/SAN-1165
Editor	Editor flow	Editor flow	Verify if an Editor is able to view the photo uploaded by a DSO.	Functional		Login to citizen/ creator. Go through all the steps and create pre-pay / postpay application Go until DSO login. Login as DSO, and upload the photo.	Photo should be uploaded.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	Verify if an Editor is able to view the photo uploaded by a DSO.	Functional		Login to citizen/creator. Go through all the steps and create pre-pay/post-pay application. Go until DSO login. Login as DSO, upload the photo. Login as editor, and check photos uploaded by DSO are viewable.	Editor should able to view the photo in the timeline.					Passed	Passed		UAT	Windows	Chrome
			https://digit-discuss.atlassian.net/browse/SAN-1037 https://digit-discuss.atlassian.net/browse/SAN-1162
			To check if the application timelines are aligned with the roles.			Go until the application updated/payment/ trips screen.	Application timelines should be aligned with the roles.					Passed	Passed		UAT	Windows	Chrome
Editor	Editor flow	Editor flow	To check photos uploaded by a DSO.			Login as editor, and check who has uploaded the photos.	Editor should be able to view photo uploaded by DSO.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To check the breadcrumbs in the FSTPO pages.			Login as FSTPO, and check all the breadcrumbs.	Breadcrumbs should be in the following format -Home/Inbox/vehicle log.					Passed	Passed		UAT	Windows	Chrome
FSTPO	FSTPO flow	FSTPO flow	To check if the disposing time schedule is in the AM/PM format.			Login as FSTPO, and check whether the disposal time schedule is in the AM/PM format.	FSTPO should be able to select AM/PM in the disposal scheduling page.					Passed	Passed		UAT	Windows	Chrome
			https://digit-discuss.atlassian.net/browse/SAN-1075 https://digit-discuss.atlassian.net/browse/SAN-1160
UI_UX			Verify the UI UX enhancements in citizen and employee logins			Login as citizen/employee. Validate the following UI UX enhancements: Log in as citizen, in service request text change in trip number screen in create application. Login as citizen, in trip number screen in citizen side, number of trips will be on top and vehicle capacity will be at the bottom. Login as DSO, localisation should be changed from scheduled to update trips. Login as citizen, all location and pit details should be combined under property details.	In UI UX AUDIT: In service request text change in trip number screen in create application should be created. Citizen should be viewable in trip number screen in citizen side. The number of trips will be on top and vehicle capacity will be at the bottom. Schedule localisation should be changed to update trips. Location and pit details should be under property details.					Passed	Passed		UAT	Windows	Chrome
			https://digit-discuss.atlassian.net/browse/SAN-848 https://digit-discuss.atlassian.net/browse/SAN-1169
Employee	Employee flow	Employee flow	Dashboard should have a pie chart for gender, revenue by usage type, application preference, customer rating, request status, and data. Apply all the drill-down (by date, ULB) on the payment chart. Dashboard should be on mobile and desktop versions. The dashboard chart should be shareable and downloadable			Login using dashboard credentials.	Dashboard should display the pie chart for gender, revenue by usage type, application preference, customer rating, request status, and data, and apply all the drill-down. Dashboard should be viewable in both mobile and desktop versions and it should be in shareable and downloadable formats.					Passed	Passed		UAT	Windows	Chrome

UAT Regression Test Cases

Regression

Test ID	Sub-feature/use case	Test ideas	Test type	Test data	Steps to be executed	Expected result	QA review	Dev review	PM review	Actual result	QA status	Dev status	Comments	Environment	OS
		Test Cases
	Citizen flow	https://digit-discuss.atlassian.net/browse/SAN-795
FSM/Citizen/01	Citizen flow	Validate that Citizen is able to verify new field "Number of Trips" on citizen feedback page_With English and Hindi Language.	Functional		Login as Citizen. Go to my application. Citizen should be able to see the completed application. Validate that citizen is able to verify new field "Number of Trips" on the citizen feedback page in EN & Hindi.	Citizen is able to verify the new field "Number of Trips" on the citizen feedback page In EN. Citizen is able to verify new field "कुल फेरों की संख्या" on the citizen feedback page_Hindi.	Done	Done		Citizen is able to verify new field "Number of Trips" on the citizen feedback page In EN. Citizen is able to verify new field "कुल फेरों की संख्या" on the citizen feedback page_Hindi.	PASSED	Done		UAT	Windows	Google Chrome
FSM/Citizen/02	Citizen flow	Validate Citizen is able to add integer from dropdown field on the citizen feedback page_Hindi/English.	Functional		Login as Citizen. Go to my application. Citizen should be able to see the completed application. Validate that citizen is able to add integer from the dropdown field on the citizen feedback page. Validate that citizen is able to submit the feedback along with proper rating and comments.	Citizen is able to add integer from 1-10, from the dropdown, and submit the feedback.	Done	Done		Citizen will be able to Add integer from 1-10 from drop down and will be able to submit the feedback	PASSED	Done		UAT	Windows	Google Chrome
FSM/Citizen/03	Citizen flow	Validate that the total number of trips field should not be mandatory for feedback submission _Hindi/English.	Functional		Login as Citizen. Go to my application. Citizen should be able to see the completed application. Validate that citizen is able to submit the feedback without total number of field trips.	Citizen will be able to submit the feed back without Total num of Field trips	Done	Done		Citizen will be able to submit the feed back without Total num of Field trips	PASSED	Done		UAT	Windows	Google Chrome
FSM/Citizen/04	Citizen flow	Validate that Datamart file should ge updated.	Functional		Login as Citizen. Go to my application. Citizen should be able to see the completed application. Citizen has completed the feedback form. Run the Query for CSV Datamart file generation. Validate that Datamart file should ge updated with the feedback details.	User is able to validate that Datamart file should ge updated	Done	Done		User is able to Validate that Datamart file should ge updated	PASSED	Done		UAT	Windows	Google Chrome
	Citizen flow	https://digit-discuss.atlassian.net/browse/SAN-736
FSM/Citizen/05	Citizen flow	Validate that citizen gender info is captured on new application right after the OTP step with citizen login_English_Male.	Functional		Login as a Citizen in the mSeva portal. Navigate to FSM. Citizen creates new application. Validate that citizen gender info is captured on new application as Male right after the OTP step. Validate if citizen is able to complete the request further with the required details. Validate that citizen should not see gender information on the application summary view.	1. citizen gender info is Captured on New application as Male right after OTP step 2. Citizen shouldn’t see gender information on the application summary view	Done	Done		1. citizen gender info is Captured on New application as Male right after OTP step 2. Citizen shouldn’t see gender information on the application summary view	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/06	Citizen flow	Validate that citizen gender info is captured on new application right after the OTP step with citizen login_Hindi_Female.	Functional		Login as a Citizen in the mSeva portal. Navigate to FSM. Citizen creates new application. Validate that citizen gender info is captured on new application as Female right after the OTP step. Validate if citizen is able to complete the request further with the required details. Validate that citizen should not see gender information on the application summary view.	1. citizen gender info is Captured on New application as Female right after OTP step 2. Citizen shouldn’t see gender information on the application summary view	Done	Done		1. citizen gender info is Captured on New application as Female right after OTP step 2. Citizen shouldn’t see gender information on the application summary view	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/07	Citizen flow	Validate that citizen gender info is captured on new application right after the OTP step with Employee Creator login_English_Transgender.	Functional		Login as a Citizen in the mSeva portal. Navigate to FSM. Citizen creates new application. Validate that citizen gender info is captured on new application as Transgender right after the OTP step. Validate if citizen is able to complete the request further with the required details. Validate that citizen should not see gender information on the application summary view.	1. citizen gender info is Captured on New application as Transgender right after OTP step 2. Citizen shouldn’t see gender information on the application summary view	Done	Done		1. citizen gender info is Captured on New application as Transgender right after OTP step 2. Citizen shouldn’t see gender information on the application summary view	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/08	Citizen flow	Validate that citizen gender info is captured on New application right after the OTP step with Employee Creator login_Hindi_Others.	Functional		Login as a Citizen in the mSeva portal. Navigate to FSM. Citizen creates new application. Validate that citizen gender info is captured on new application as Others right after the OTP step. Validate if citizen is able to complete the request further with the required details. Validate that citizen should not see gender information on the application summary view.	1. citizen gender info is Captured on New application as Others right after OTP step 2. Citizen shouldn’t see gender information on the application summary view	Done	Done		1. citizen gender info is Captured on New application as Others right after OTP step 2. Citizen shouldn’t see gender information on the application summary view	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/09	Citizen flow	Validate that Citizen gender step is skippable with Citizen Login_Hindi.	Functional		Login as a Citizen in the mSeva portal. Navigate to FSM. Citizen creates new application. Validate that citizen gender step is skippable.	It is Validated that Citizen gender step is skippable in Citizen Logins	Done	Done		It is Validated that Citizen gender step is skippable in Citizen Logins	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/10	Citizen flow	Validate that Citizen gender step is skippable with Employee Creator Login_English.	Functional		Login as an Employee Creator in the mSeva portal. Navigate to FSM. Citizen creates new application. Validate that citizen gender step is skippable.	It is Validated that Citizen gender step is skippable in Employee creator Logins	Done	Done		It is Validated that Citizen gender step is skippable in Employee creator Logins	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/11	Citizen flow	Validate that Employee editor is able to view the gender of the applicant on the application summary view_Hindi.	Functional		Login as an Employee editor in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that employee is able to view the gender of the applicant on the application summary view.	Employee is able to view the gender of the applicant on the application summary view	Done	Done		Employee is able to view the gender of the applicant on the application summary view	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/12	Citizen flow	Validate that DSO is not able to view the gender of the applicant on the application summary view_English.	Functional		1.Login as a DSO in mSeva Portal 2.Navigate to FSM 3.Search for application and Click on Take action 4.Validate that DSO is not able to view the gender of the applicant on the application summary view	DSO is not able to view the gender of the applicant on the application summary view	Done	Done		DSO is not able to view the gender of the applicant on the application summary view	PASSED			UAT	Windows	Google Chrome
		DSO Specific Test Cases
	DSO flow	https://digit-discuss.atlassian.net/browse/SAN-802
FSM/DSO/01	DSO flow	Validate the message when unregistered phone number is entered in DSO login_English.	Functional		Login to the mSeva portal. Navigate to FSM. User click on DSO login. Validate message when unregistered phone number is entered in DSO login: Please use a registered number for logging as a DSO.	Validate message when unregistered phone number is entered in DSO login: Please use a registered number for logging as a DSO.	Done	Done		validate message when unregistered phone number is entered in DSO login: Please use a registered number for logging as a DSO	PASSED			UAT	Windows	Google Chrome
FSM/DSO/02	DSO flow	Validate the message when unregistered phone number is entered in DSO login_Hindi.	Functional		Login to the mSeva portal. Navigate to FSM. User click on DSO login. Validate message when unregistered phone number is entered in DSO login: कृपया डीएसओ के रूप में लॉगिंग के लिए पंजीकृत नंबर का उपयोग करें.	Validate message when unregistered phone number is entered in DSO login: कृपया डीएसओ के रूप में लॉगिंग के लिए पंजीकृत नंबर का उपयोग करें	Done	Done		Validate message when unregistered phone number is entered in DSO login: कृपया डीएसओ के रूप में लॉगिंग के लिए पंजीकृत नंबर का उपयोग करें	PASSED			UAT	Windows	Google Chrome
FSM/DSO/03	DSO flow	Validate when DSO logins with registered phone number, DSO is able to see the application_English.	Functional		Login to the mSeva portal. Navigate to FSM. User click on DSO login. Validate when DSO logins with registered phone number, DSO is able to see the application.	Validate when DSO login with registered phone number is able to see the application	Done	Done		Validate when DSO login with registered phone number is able to see the application	PASSED			UAT	Windows	Google Chrome
FSM/DSO/04	DSO flow	Validate when DSO logins with registered phone number, DSO is able to see the application_Hindi.	Functional		Login to the mSeva portal. Navigate to FSM. User click on DSO login. Validate when DSO logins with registered phone number, DSO is able to see the application.	Validate when DSO login with registered phone number is able to see the application	Done	Done		Validate when DSO login with registered phone number is able to see the application	PASSED			UAT	Windows	Google Chrome
	DSO flow	https://digit-discuss.atlassian.net/browse/SAN-817
FSM/DSO/05	DSO flow	Validate that DSO can edit the property type and property sub type for an application_English.	Functional		Login as a DSO in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that DSO can edit the property type and property sub type for an application. Validate DSO is able to submit the request further with the required details. Validate property type and sub type info is updated in Datamart.	DSO will be able to edit the property type and property sub type for a application 2.Validate that property type and sub type info is updated in Datamart	Done	Done		1.DSO will be able to edit the property Type and Property Sub Type for a application 2.Validate that property type and sub type info is updated in Datamart	PASSED			UAT	Windows	Google Chrome
FSM/DSO/06	DSO flow	Validate that DSO can edit the pit details for an application_English	Functional		Login as a DSO in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that DSO can edit the pit type and pit dimension and upload a pit photo for an application. Validate DSO is able to submit the request further with required details.	1.DSO will be able to edit the Pit Type and Pit Dimension and Upload a PIT photo for a application	Done	Done		1.DSO will be able to edit the Pit Type and Pit Dimension and Upload a PIT photo for a application	PASSED			UAT	Windows	Google Chrome
FSM/DSO/07	DSO flow	Validate that DSO can edit the property type and property sub type for an application_Hindi.	Functional		Login as a DSO in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that DSO can edit the property type and property sub type for an application. Validate DSO is able to submit the request further with the required details. Validate property type and sub type info is updated in Datamart.	1.DSO will be able to edit the property Type and Property Sub Type for a application 2.Validate that property type and sub type info is updated in Datamart	Done	Done		1.DSO will be able to edit the property Type and Property Sub Type for a application 2.Validate that property type and sub type info is updated in Datamart	PASSED			UAT	Windows	Google Chrome
FSM/DSO/08	DSO flow	Validate that DSO can edit the pit details for an application_Hindi.	Functional		Login as a DSO in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that DSO can edit the pit type and pit dimension, and upload a pit photo for an application. 5.Validate if DSO is able to submit the request further with the required details.	1.DSO will be able to edit the Pit Type and Pit Dimension and Upload a PIT photo for a application	Done	Done		1.DSO will be able to edit the Pit Type and Pit Dimension and Upload a PIT photo for a application	PASSED			UAT	Windows	Google Chrome
FSM/DSO/09	DSO flow	Validate that DSO cannot modify the applicant and the property address for an application_Hindi.	Functional		Login as a DSO in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that DSO cannot modify the applicant and the property address for an application.	1.DSO will not be able to edit the applicant and the property address for a application	Done	Done		1.DSO will not be able to edit the applicant and the property address for a application	PASSED			UAT	Windows	Google Chrome
FSM/DSO/10	DSO flow	Validate that DSO cannot modify the possible service date_English.	Functional		Login as a DSO in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that DSO cannot modify the possible service date for an application.	1.DSO will not be able to modify the possible service date for a application	Done	Done		1.DSO will not be able to modify the possible service date for a application	PASSED			UAT	Windows	Google Chrome
FSM/DSO/11	DSO flow	Validate that DSO should not be able to modify old applications (i.e. service date < current date) or applications in citizen feedback pending status_Hindi/English.	Functional		Login as a DSO in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that DSO should not be able to modify old applications (i.e. service date < current date) or applications in citizen feedback pending status.	1.DSO will not be able to modify old applications (i.e. service date < current date) or applications in citizen feedback pending status	Done	Done		1.DSO will not be able to modify old applications (i.e. service date < current date) or applications in citizen feedback pending status	PASSED			UAT	Windows	Google Chrome
		Employee Specific Test Cases
	Employee flow	https://digit-discuss.atlassian.net/browse/SAN-818
FSM/Emp/01	Employee flow	Validate ULB Employee selects vehicle capacity instead of vehicle Type_English_Employee Editor.	Functional		Login as an Employee Editor in the mSeva Portal. Navigate to FSM. Search for application and click on take action. Validate that a ULB employee is able to select vehicle capacity from the dropdown. Validate that vehicle type is not present in the form. Validate that employee is able to submit the request further.	ULB employee should be able to select the vehicle capacity from the drop down. ULB Employee does not see the vehicle type in the entire form. ULB employee is able to submit the request further.	Done	Done		1) ULB Employee should be able to select vehicle capacity from the drop down 2)ULB Employee doesn’t see the Vechile Type in the entire form 3)ULB Employee is able to Submit the Request further	PASSED			UAT	Windows	Google Chrome
FSM/Emp/02	Employee flow	Validate ULB Employee selects vehicle capacity instead of vehicle Type_Hindi_Employee Editor.	Functional		Login as an Employee Editor in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that a ULB employee is able to select vehicle capacity from the dropdown. Validate that vehicle type is not present in the form. Validate that employee is able to submit the request further.	ULB employee should be able to select the vehicle capacity from the drop down. ULB employee does not see the vehicle type in the entire form. ULB employee is able to submit the request further.	Done	Done		1) ULB Employee should be able to select vehicle capacity from the drop down 2)ULB Employee doesn’t see the Vechile Type in the entire form 3)ULB Employee is able to Submit the Request further	PASSED			UAT	Windows	Google Chrome
FSM/Emp/03	Employee flow	Validate ULB Employee selects vehicle capacity instead of vehicle Type_English_Employee Creator.	Functional		Login as an Employee Creator in the mSeva portal. Navigate to FSM. Validate that a ULB employee is able to select vehicle capacity from the dropdown. Validate that vehicle type is not present in the form. Validate that employee is able to submit the request further.	ULB employee should be able to select the vehicle capacity from the drop down. ULB employee does not see the vehicle type in the entire form. ULB employee is able to submit the request further.	Done	Done		1) ULB Employee should be able to select vehicle capacity from the drop down 2)ULB Employee doesn’t see the Vechile Type in the entire form 3)ULB Employee is able to Submit the Request further	PASSED			UAT	Windows	Google Chrome
FSM/Emp/04	Employee flow	Validate ULB Employee selects vehicle capacity instead of vehicle Type_Hindi_Employee Creator.	Functional		Login as an Employee Creator in the mSeva portal. Navigate to FSM. Validate that a ULB employee is able to select vehicle capacity from the dropdown. Validate that vehicle type is not present in the form. Validate that employee is able to submit the request further.	ULB employee should be able to select the vehicle capacity from the drop down. ULB employee does not see the vehicle type in the entire form. ULB employee is able to submit the request further.	Done	Done		1) ULB Employee should be able to select vehicle capacity from the drop down 2)ULB Employee doesn’t see the Vechile Type in the entire form 3)ULB Employee is able to Submit the Request further	PASSED			UAT	Windows	Google Chrome
		Datamart Specific Test Cases
	Datamart	https://digit-discuss.atlassian.net/browse/SAN-786
FSM/Datamart/01- data mart not ready in QA	Datamart validation	Validate that gender information is present in FSM application in Datamart as Male.	Functional		Run the query for CSV Datamart file generation. Validate that gender information is present in FSM application in Datamart as Male.	It should be Validated that gender information is present in FSM application in Datamart as Male.	Done	Done		It should be Validated that gender information is present in fsm application in datamart as Male				UAT	Windows	Google Chrome
FSM/Datamart/02-data mart not ready in QA	Datamart validation	Validate that gender information is present in FSM application in Datamart as Female.	Functional		Run the query for CSV Datamart file generation. Validate that gender information is present in FSM application in Datamart as Female.	It should be validated that gender information is present in FSM application in Datamart as Female.	Done	Done		It should be Validated that gender information is present in fsm application in datamart as Female				UAT	Windows	Google Chrome
FSM/Datamart/03-data mart not ready in QA	Datamart validation	Validate that gender information is present in FSM application in Datamart as Transgender.	Functional		Run the query for CSV Datamart file generation. Validate that gender information is present in FSM application in Datamart as Transgender.	It should be validated that gender information is present in FSM application in Datamart as Transgender.	Done	Done		It should be Validated that gender information is present in fsm application in datamart as Transgender				UAT	Windows	Google Chrome
FSM/Datamart/04-data mart not ready in QA	Datamart validation	Validate that gender information is present in FSM application in Datamart as Others.	Functional		Run the query for CSV Datamart file generation. Validate that gender information is present in FSM application in Datamart as Others.	It should be validated that gender information is present in FSM application in Datamart as Others.	Done	Done		It should be Validated that gender information is present in fsm application in datamart as Others				UAT	Windows	Google Chrome
FSM/Datamart/05-data mart not ready in QA	Datamart validation	Validate that gender information present in FSM application in Datamart as "Not Known".	Functional		Run the query for CSV Datamart file generation. Validate that gender information is present in FSM application in Datamart as 'Not Known".	It should be validated that gender information is present in FSM application in Datamart as "Not Known."	Done	Done		It should be Validated that gender information is present in fsm application in datamart as "Not Known"				UAT	Windows	Google Chrome
		DSO Specific Test Cases
	DSO flow	https://digit-discuss.atlassian.net/browse/SAN-790
DSO_01	DSO flow	Check whether "Try updating the pit details, it should allow the user to update the pit details."	Functional		Login as citizen and create an application. Login as editor and update application to make payment. Login as collector and make the payment. Login as editor, update pit details, and assign DSO. Login as DSO and try updating the pit details. It should allow the user to update the pit details.	Try updating the pit details, it should allow the user to update the pit details.	Done	Done		Try updating the pit details, it should allow the user to update the pit details.	PASSED			UAT	Windows	Google Chrome
DSO_02	DSO flow	Check whether "DSO shouldn’t be able to modify old applications (i.e. desludging date < current date) or applications in citizen feedback pending status."	Functional		Login as citizen and create an application. Login as editor and update application to make the payment. Login as collector and make the payment. Login as editor, update pit details, and assign DSO. Login as DSO. DSO should not be able to modify old applications (i.e. desludging date < current date) or applications in citizen feedback pending status.	DSO should not be able to modify old applications (i.e. desludging date < current date) or applications in citizen feedback pending status.	Done	Done		DSO shouldn’t be able to modify old applications (i.e. desludging date < current date) or applications in citizen feedback pending status	PASSED			UAT	Windows	Google Chrome
DSO_03	DSO flow	Check whether "DSO can add pit photo."	Functional		Login as citizen and create an application. Login as editor and update application to make the payment. Login as collector and make the payment. Login as editor, update pit details, and assign DSO. Login as DSO, who can add pit photo.	DSO can add pit photo	Done	Done		DSO can add pit photo	PASSED
DSO_04	DSO flow	Check whether pre-selected property and pit details should be shown. If no value is present, then show - and data from MDMS in the dropdown.	Functional		Login as citizen and create an application. Login as editor and update application to make the payment. Login as collector and make the payment. Login as editor, update pit details, and assign DSO. Login as DSO. Pre-selected property and pit details should be shown. If no value is present, then show - and data from MDMS in the dropdown.	Pre-selected property and pit details should be shown. If no value is present, then show - and data from MDMS in the dropdown.	Done	Done		Pre-selected Property and Pit details should be shown. If no value is present, then show - and data from mdms in the drop-down	PASSED
DSO_05	DSO flow	Check whether this will need to be a role based edit. It can be edited by roles: DSO, editor.	Functional		Login as citizen and create an application. Login as editor and update application to make the payment. Login as collector and make the payment. Login as editor, update pit details, and assign DSO. Login as DSO. This will need to be a role-based edit. This can be edited by roles = DSO, editor.	This will need to be a role based edit. This can be edited by roles = DSO, editor.	Done	Done		This will need to be a role based edit. This can be edited by roles = dso, editor	PASSED
DSO_06	DSO flow	Check whether the application should be editable in: Pending for DSO approval, DSO InProgress status.	Functional		Login as citizen and create an application. Login as editor and update application to make the payment. Login as collector and make the payment. Login as editor, update pit details, and assign DSO. Login as DSO. The application should be editable in: Pending for DSO approval, DSO InProgress status.	The application should be editable in: Pending for DSO approval, DSO InProgress status.	Done	Done		the application should be editable in: Pending for DSO approval, DSO InProgress status	PASSED
		DSO Specific Test Cases
	DSO flow	https://digit-discuss.atlassian.net/browse/SAN-790
Vehicle_01	Employee flow	Check whether Vehicle Capacity is a mandatory field.	Functional		Login as a Employee editor in the mSeva portal. Navigate to FSM. Validate that a ULB employee is able to select vehicle capacity from the dropdown.	Vehicle capacity is a mandatory field.	Done	Done		Vehicle Capacity is a mandatory field	PASSED			UAT	Windows	Google Chrome
Vehicle_02	Employee flow	Check whether Vehicle Capacity should show unique capacity value from the master data.	Functional		Login as a Employee editor in the mSeva portal. Navigate to FSM. Validate that a ULB employee is able to select vehicle capacity from the dropdown.	Vehicle capacity should show unique capacity value from the master data.	Done	Done		Vehicle Capacity should show unique capacity value from master data	PASSED
Vehicle_03	Employee flow	Check whether Vehicle Capacity should show unique capacity value from the master data.	Functional		Login as a Employee editor in the mSeva portal. Navigate to FSM. Validate that a ULB employee is able to select vehicle capacity from the dropdown.	Vehicle capacity should show unique capacity value from the master data.	Done	Done		Vehicle Capacity should show unique capacity value from master data	PASSED
Vehicle_04	Employee flow	Check whether Vehicle Type is not shown on any user interface.	Functional		Login as a Employee editor in the mSeva portal. Navigate to FSM. Validate that a ULB employee is able to select vehicle capacity from the dropdown.	Vehicle type is not shown on any user interface.	Done	Done		Vehicle Type is not shown on any user interface	PASSED
Vehicle_05	Employee flow	Ensure that the logic for assignment of DSO is not changed with this ticket.	Functional		Login as a Employee editor in the mSeva portal. Navigate to FSM. Validate that a ULB employee is able to select vehicle capacity from the dropdown.	Ensure that the logic for assignment of DSO is not changed with this ticket.	Done	Done		Ensure that the logic for assignment of DSO is not changed with this ticket	PASSED
Test ID	Sub Feature/ Use Case	Test Ideas	Test Type	Test data	Steps to be executed	Expected Result	QA Review	Dev Review	PM Review	Actual result	QA Status	Dev Status	Comments	Environment	OS	Browser
		DSO Specific Test Cases
	DSO flow	https://digit-discuss.atlassian.net/browse/SAN-823
FSM/DSO/01	DSO flow	Check whether DSO gender addition is during DSO creation.	Functional		User requests search DSO API. User can see the gender info for that DSO in return.	User should be able to create new DSO with gender info using create DSO API and can verify the gender info using search API.	Done	Done		User should be able to Create new DSO with Gender info using Create DSO API and can Verify the gender info using search API.	PASSED			UAT	Windows	Google Chrome
FSM/DSO/02	DSO flow	Check whether search API is updated so that DSO gender can be returned.	Functional		User requests search DSO API. User can see the gender info for that DSO in return.	DSO gender is returned when search DSO request is triggered.	Done	Done		DSO gender is returned when Search DSO request is Triggered	PASSED			UAT	Windows	Google Chrome
FSM/DSO/03	DSO flow	Validate If DSO is registered as Citizen, then it should show Gender.	Functional		Citizen is registered as DSO. User requests search DSO API. User can see the gender info for that DSO in return.	If citizen is registered as DSO, then gender info should be returned.	Done	Done		Citizen is registered as DSO then Gender info should be returned	PASSED			UAT	Windows	Google Chrome
FSM/DSO/04	DSO flow	Validate update API is updating gender info for existing DSOs.	Functional		User request update API for updating gender information for existing DSOs. User requests search DSO API. User can see the gender info for that DSO in return.	User should be able to request the update API for existing DSOs with gender info.	Done	Done		User should be able to request update API for existing DSOs with gender info	PASSED			UAT	Windows	Google Chrome
FSM/DSO/05-- Datamart related	DSO flow	Validate that DSO gender information is present in Datamart as Male/Female/Transgender/other in "DSO gender" column.	Functional		Complete any application. Run the query for CSV Datamart file generation. Validate that gender information is present in Datamart as Male/Female/Transgender/other in "DSO gender" column.	User should be able to validate that gender information is present in Datamart as Male/Female/Transgender/other in "DSO gender" column.	Done	Done		User should be able to Validate that gender information is present in datamart as Male/Female/Transgender/other in "DSO gender" Column	PASSED			UAT	Windows	Google Chrome
FSM/DSO/06	DSO flow	Citizen gender should not get overridden when DSO gender is updated from the backend (pre requisite: when citizen is a DSO also).	Functional		User request update API for updating gender info for existing DSO. User requests search DSO API. User can see the gender info for that DSO in return. Validate that citizen gender should not get overridden in UI.	User should be able to validate that citizen gender is not getting overridden when DSO gender is updated from the backend (pre-requisite: when citizen is also a DSO).	Done	Done		User should be able to validate Citizen gender is not getting overriden when DSO gender is updated from Backend (pre requisite: when Citizen is a DSO also)	PASSED			UAT	Windows	Google Chrome
FSM/DSO/07	DSO flow	DSO gender should not get overridden when citizen gender is updated from the backend (pre requisite: when citizen is a DSO also).	Functional		User request update API for updating gender info for existing citizen. User requests search citizen API. User can see the gender info for that citizen in return. Validate that DSO gender info should not get overridden in the backend.	User should be able to validate that DSO gender is not getting overridden when citizen gender is updated from the backend (pre-requisite: when citizen is also a DSO).	Done	Done		User should be able to validate DSO gender is not getting overriden when Citizen gender is updated from Backend (pre requisite: when Citizen is a DSO also)	PASSED			UAT	Windows	Google Chrome
		Employee Specific Test Cases
	Employee flow	https://digit-discuss.atlassian.net/browse/SAN-829
FSM/Emp/01	Employee flow	Validate that the "No Option Available" message should be present in dropdown when there is no vehicle present to assign in the Assign Vehicle page.	Functional		Login as an Employee Editor in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that the "No Option Available" message should be present in the dropdown on the assign vehicle page.	User should be able to validate that the "No Option Available" message is present in drop down on Assign Vehicle page.	Done	Done		User should be able to Validate that "No Option Availaible" message should be present in drop down on Assign Vechile page	PASSED			UAT	Windows	Google Chrome
FSM/Emp/02	Employee flow	Validate that list of Vehicle is present in drop down in Assign Vehicle page.	Functional		Login as an Employee Editor in the mSeva portal. Navigate to FSM. Search for application and click on take action. Validate that the list of vehicles is present in the dropdown on the assign vehicle page.	User should be able to validate that the list of vehicles is present in the dropdown on the assign vehicle page.	Done	Done		User should be able to Validate that list of Vechile is pesent in drop down in Assign Vechile page	PASSED			UAT	Windows	Google Chrome
	Employee flow	https://digit-discuss.atlassian.net/browse/SAN-803
Moved to sprint 4 FSM/Emp/03	Employee flow	Validate that the "Waiting for disposal" application status is added in filter _English.	Functional		Login as a ULB Employee in the mSeva Portal with English language. Navigate to FSM. Go to employee inbox. Validate that the "Waiting for disposal" under the "Application Status" is added in the filter. Validate "Waiting for disposal" under the “Application Status” and show “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Waiting for disposal" filter. User is able to see "Waiting for disposal" under the “Application Status” and see “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	Done	Done		1. User should be able to Filter out the application on basis of "Waiting for disposal" Filter. 2. User is able to see "Waiting for disposal" under “Application Status” and see “-” under “SLA Days Remaining” 3)Status should also reflect on application Timeline when user click on application	PASSED			UAT	Windows	Google Chrome
Moved to sprint 4 FSM/Emp/03	Employee flow	Validate that the "Disposed" application status is added in filter_English.	Functional		Login as a ULB Employee in the mSeva Portal with English language. Navigate to FSM. Go to the employee inbox. Validate "Disposed" application status is added in the filter. Validate "Disposed" under “Application Status” and show “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on basis of the "Disposed" filter. User is able to see"Disposed" under “Application Status” and “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on application.	Done	Done		1. User should be able to Filter out the application on basis of "Disposed" Filter. 2. User is able to see"Disposed" under “Application Status” and see “-” under “SLA Days Remaining” 3)Status should also reflect on application Timeline when user click on application	PASSED			UAT	Windows	Google Chrome
Moved to sprint 4 FSM/Emp/03	Employee flow	Validate that the "Citizen Feedback Pending" application status is added in filter _English.	Functional		Login as a ULB Employee in the mSeva Portal with English language. Navigate to FSM. Go to the employee inbox. Validate that "Citizen Feedback Pending" application status is added in the filter. Validate "Citizen Feedback Pending" under “Application Status” and show “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Citizen Feedback Pending" filter. User is able to show "Citizen Feedback Pending" under “Application Status” and see “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	Done	Done		1. User should be able to Filter out the application on basis of "Citizen Feedback Pending" Filter. 2. User is able to show "Citizen Feedback Pending" under “Application Status” and see “-” under “SLA Days Remaining” 3)Status should also reflect on application Timeline when user click on application	PASSED			UAT	Windows	Google Chrome
Moved to sprint 4 FSM/Emp/03	Employee flow	Validate that Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status are Present in filter_English.	Functional		Login as a ULB Employee in the mSeva Portal with English language. Navigate to FSM. Go to the employee inbox. Validate that Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status are present in the filter. Validate "Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status under “Application Status” and show “num of days” under “SLA Days Remaining.”	User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in the filter column. User is able to see the above status under “Application Status” and see “num of days” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	Done	Done		1. User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in filter column 2. User is able to see above status under “Application Status” and see “num of days” under “SLA Days Remaining” 3.Status should also reflect on application Timeline when user click on application	PASSED			UAT	Windows	Google Chrome
Moved to sprint 4 FSM/Emp/03	Employee flow	Validate that the "Waiting for disposal" application status is added in filter_Hindi.	Functional		Login as a ULB Employee in the mSeva Portal with Hindi language. Navigate to FSM. Go to the employee inbox. Validate that "Waiting for disposal" application status is added in the filter. Validate "Waiting for disposal" under “Application Status” and show “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on basis of the "Waiting for disposal" filter. User is able to see "Waiting for disposal" under “Application Status” and “-” under “SLA Days Remaining.”	Done	Done		1. User should be able to Filter out the application on basis of "Waiting for disposal" Filter. 2. User is able to see "Waiting for disposal" under “Application Status” and see “-” under “SLA Days Remaining”	PASSED			UAT	Windows	Google Chrome
Moved to sprint 4 FSM/Emp/03	Employee flow	Validate that the "Disposed" application status is added in filter_Hindi	Functional		Login as a ULB Employee in the mSeva Portal with Hindi language. Navigate to FSM. Go to the employee inbox. Validate that "Disposed" application status is added in the filter. Validate "Disposed" under “Application Status” and show “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Disposed" filter. User is able to see "Disposed" under “Application Status” and “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	Done	Done		1. User should be able to Filter out the application on basis of "Disposed" Filter. 2. User is able to see"Disposed" under “Application Status” and see “-” under “SLA Days Remaining” 3.Status should also reflect on application Timeline when user click on application	PASSED			UAT	Windows	Google Chrome
Moved to sprint 4 FSM/Emp/03	Employee flow	Validate that the "Citizen Feedback Pending" application status is added in filter_Hindi.	Functional		Login as a ULB Employee in the mSeva Portal with Hindi language. Navigate to FSM. Go to the employee inbox. Validate that the "Citizen Feedback Pending" application status is added in the filter. Validate "Citizen Feedback Pending" under “Application Status” and show “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Citizen Feedback Pending" filter. User is able to show "Citizen Feedback Pending" under “Application Status” and see “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	Done	Done		1. User should be able to Filter out the application on basis of "Citizen Feedback Pending" Filter. 2. User is able to show "Citizen Feedback Pending" under “Application Status” and see “-” under “SLA Days Remaining” 3.Status should also reflect on application Timeline when user click on application	PASSED			UAT	Windows	Google Chrome
Moved to sprint 4 FSM/Emp/03	Employee flow	Validate that Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status are Present in filter_Hindi.	Functional		Login as a ULB Employee on the mSeva Portal with Hindi language. Navigate to FSM. Go to the employee inbox. Validate that Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status are present in the filter. Validate "Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status under “Application Status” and show “num of days” under “SLA Days Remaining.”	User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in the filter column. User is able to see the above status under “Application Status” and “num of days” under “SLA Days Remaining.”	Done	Done		1. User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in filter column 2. User is able to see above status under “Application Status” and see “num of days” under “SLA Days Remaining”	PASSED			UAT	Windows	Google Chrome
		Test Cases
	Citizen flow	https://digit-discuss.atlassian.net/browse/SAN-830
FSM/Citizen/01	Citizen flow	Validate Citizen is able to make payment once ULB employee validation is done.	Functional		Login as a Citizen. Navigate to FSM. Search for application and click on take action. Validate that citizen is able to make payment once ULB employee validation is done.	User should be able to validate that a citizen is able to make payment once ULB employee validation is done.	Done	Done		User should be able to Validate Citizen is able to Make Payment once ULB employee validation is done	PASSED			UAT	Windows	Google Chrome
	Citizen flow	https://digit-discuss.atlassian.net/browse/SAN-688
FSM/Citizen/02	Citizen flow	Validate Citizen is able to see the helpline number on hamburger menu_English.	Functional		Login as a Citizen with English Language. Navigate to FSM. Validate that citizen is able to see the helpline number on the hamburger menu.	Citizen should be able to see the helpline number on the hamburger menu.	Done	Done		Citizen should be able to see Helpline number on hamburger menu	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/03	Citizen flow	Helpline link should be clickable and trigger call function for the entered number_English.	Functional		Login as a Citizen with English language. Navigate to FSM. Validate that a citizen is able to see the helpline number on the hamburger menu. Helpline link should be clickable and trigger a call function for the entered number.	Citizen should be able to click the helpline link and trigger a call function for the entered number.	Done	Done		Citizen should be able to click Helpline link and trigger call function for the entered number	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/04	Citizen flow	Validate Citizen is able to see the helpline number on hamburger menu_Hindi	Functional		Login as a Citizen with Hindi language. Navigate to FSM. Validate that citizen is able to see the helpline number on the hamburger menu.	Citizen should be able to see the helpline number on the hamburger menu.	Done	Done		Citizen should be able to see Helpline number on hamburger menu	PASSED			UAT	Windows	Google Chrome
FSM/Citizen/05	Citizen flow	Helpline link should be clickable and trigger call function for the entered number_Hindi.	Functional		Login as a Citizen with Hindi language. Navigate to FSM. Validate that citizen is able to see the helpline number on the hamburger menu. Helpline link should be clickable and trigger a call function for the entered number.	Citizen should be able to click the helpline link and trigger a call function for the entered number.	Done	Done		Citizen should be able to click Helpline link and trigger call function for the entered number	PASSED			UAT	Windows	Google Chrome
		FSTPO Specific Test Cases
	FSTPO flow	https://digit-discuss.atlassian.net/browse/SAN-800
FSM/FSTPO/01	FSTPO flow	Validate that the Decline Vehicle action should be added for FSTPO, with predefined reasons and conditional comment option.	Functional		Login as FSTPO. Navigate to FSM. Search for application and click on take action. Validate that the decline vehicle action with predefined reasons and conditional comment option is added for FSTPO.	User should be able to validate that decline vehicle action with predefined reasons and conditional comment option is added for FSTPO.	Done	Done		User should be able to Validate Decline Vehicle action with predefined reasons and conditional comment option is added for FSTPO	PASSED			UAT	Windows	Google Chrome
FSM/FSTPO/02	FSTPO flow	Validate that Reason for Declining is a mandatory Field.	Functional		Login as FSTPO with English/Hindi language. Navigate to FSM. Search for application and click on take action. FSTPO clicks on the decline vehicle button without choosing a reason for declining. Validate error msg: This field cannot be empty.	Reason for declining is a mandatory field.	Done	Done		Reason for Declining is a Mandatory Field	PASSED			UAT	Windows	Google Chrome
FSM/FSTPO/03	FSTPO flow	Validate when 'others' is selected as Reason for Declining, then 'Comments' input box appear, which is mandatory field.	Functional		Login as FSTPO with English/Hindi language. Navigate to FSM. Search for application and click on take action. FSTPO selects "Others" in the reason for declining field. Validate that the "comments" input box appears. FSTPO clicks on the decline vehicle button without entering anything in the "comments" input box. Validate error msg: This field cannot be empty.	If "others" is selected as the reason for declining, then the "Comments" input box should appear as it is a mandatory field.	Done	Done		If "others" is selected as the reason for declining, then "Comments" input box will appear, which is mandatory field	PASSED			UAT	Windows	Google Chrome
FSM/FSTPO/04	FSTPO flow	Validate that after declining from FSTPO, the vehicle trip will be in “TRIP DECLINED” status.	Functional		Login as FSTPO with English/Hindi language. Navigate to FSM. Search for application and click on take action. FSTPO selects the reason for declining and clicks on the "decline vehicle" button. Validate that vehicle trip will be in “TRIP DECLINED” status.	Validate that after being declining by FSTPO, the vehicle trip should be in “TRIP DECLINED” status.	Done	Done		Validate after declining from FSTPO, that the vehicle trip is in the “TRIP DECLINED” status.	PASSED			UAT	Windows	Google Chrome
FSM/FSTPO/05	FSTPO flow	Validate that declining a vehicle will not require vehicle out-time.	Functional		Login as a FSTPO with English/Hindi language. Navigate to FSM. Search for application and click on take action. FSTPO selects the reason for declining and clicks on the "decline vehicle" button. Validate that vehicle trip will be in “TRIP DECLINED” status.	Validate that declining a vehicle should not require vehicle out-time.	Done	Done		Validate that declining a vehicle should not require a vehicle out-time.	PASSED			UAT	Windows	Google Chrome
FSM/FSTPO/06	FSTPO flow	Validate that Datamart is getting updated with trip declined status and the reason for declining column.	Functional		FSTPO declines the trip. Run the query for CSV Datamart file generation. Validate that Datamart is getting updated with trip declined status and the reason for declining column.	Datamart should be updated with trip declined status and the reason for declining column.	Done	Done		Datamart should be updated with the trip declined status and the reason for declining column.	PASSED			UAT	Windows	Google Chrome
		SMS Text EN and Hindi testing is also required
		Dashboard Specific Test Cases
	FSM DSS flow	https://digit-discuss.atlassian.net/browse/SAN-785
FSM/DSS/01	FSM DSS flow	Validate a pie-chart for request by gender in the FSM dashboard on desktop.	Functional		Login as FSM DSS in the mSeva portal on desktop. Navigate to the dashboard and then to FSM. Validate that a pie-chart for request by gender in FSM DSS dashboard is present.	It is validated that a pie-chart for request by gender in FSM DSS dashboard is present in the desktop version.	Done	Done		It is validated that a pie-chart for request by gender in the FSM DSS dashboard is present in the desktop version.	PASSED			UAT	Windows	Google Chrome
FSM/DSS/02	FSM DSS flow	Validate that the view of the DSS dashbord is in 2x2 (ColumnxRow).	Functional		Login as FSM DSS in the mSeva portal. Navigate to the dashboard and then to FSM. Validate that the view of the DSS dashbord is in 2x2 (ColumnxRow).	It is validated that the view of the DSS dashbord is in 2x2 (ColumnxRow).	Done	Done		It is validated that the view of the DSS dashboard is in 2x2 (ColumnxRow).	PASSED			UAT	Windows	Google Chrome
FSM/DSS/03	FSM DSS flow	Validate that the DSS dashboard is seen with gender info on mobile.	Functional		Login as FSM DSS in mSeva Portal on mobile. Navigate to the dashboard and then to FSM. Validate that the DSS dashboard is seen with gender info on mobile.	It is validated that the DSS dashboard is seen with gender info in on mobile.	Done	Done		It is validated that the DSS dashboard is seen with the gender info on mobile.	PASSED			UAT	Windows	Google Chrome
FSM/DSS/04	FSM DSS flow	Validate that the FSM dashboard is shareable and can be downloaded in PDF.	Functional		Login as FSM DSS in the mSeva portal on mobile. Navigate to the dashboard and then to FSM. Validate that the DSS dashboard is sharable. Validate that the DSS dashboard can be downloaded in PDF.	It is validated that the DSS dashboard is shareable and can be downloaded.	Done	Done		It is validated that the DSS dashboard is shareable and can be downloaded.	PASSED			UAT	Windows	Google Chrome
Test ID	Login with	Sub Feature/ Use Case	Test Ideas	Test Type	Test data	Steps to be executed	Expected Result	QA Review	Dev Review	PM Review	Actual result	QA Status	Dev Status	Comments	Environment	OS
			Test Cases
		Citizen Flow	https://digit-discuss.atlassian.net/browse/SAN-849
FSM/Citizen/01	Citizen	Citizen Flow	Check whether Citizen is able to see the Choice of payment as "Pay Now" or "Pay on Service"_English.	Functional	107-FSM-2022-02-23-005235	Login as Citizen with English language. Citizen enters OTP. They should be able to select the payment preference screen. Citizen is able to see the choice of payment as "Pay Now" or "Pay on Service." Citizen is also able to see the info message about when to make the payment as mentioned in SAN-842.	Citizen is able to see the choice of payment as "Pay Now" or "Pay on Service" with the info message.	Done	Done		Citizen is able to see the Choice of payment as "Pay Now" or "Pay on Service" with the info message.	PASSED			UAT	Windows
FSM/Citizen/02	Citizen	Citizen Flow	Check whether Citizen is able to select the choice of payment as "Pay Now" _English.	Functional	107-FSM-2022-02-23-005235	Login as Citizen with English language. Citizen enters the OTP. They should be able to select the payment preference screen. Citizen is able to select the choice of payment as "Pay Now" and verify that pre-service workflow should be applied to the application. Citizen should read the info based on the payment type selected in the first screen. and the other screens (review application and property type) as mentioned in SAN-842.	Citizen is able to select the choice of payment as "Pay Now" and see the info message in the review application and property type screen.			Reviewed	Citizen is able to select the choice of payment as "Pay Now" and see the info message in the review application and property type screen.				UAT	Windows
FSM/Citizen/03	Citizen	Citizen Flow	Check whether Citizen is able to select the choice of payment as "Pay on Service" _English.	Functional	107-FSM-2022-02-23-005236	Login as Citizen with English language. Citizen enters the OTP. They should be able to select the payment preference screen. Citizen is able to select the choice of payment as "Pay on Service" and verify that post-service workflow is applied to the application. Citizen should read the info based on the payment type selected in the first screen and the other screens (review application and property type) as mentioned in SAN-842.	Citizen is able to select the choice of payment as "Pay on Service" and see the info message in the review application and property type screen.			Reviewed	Citizen is able to select the choice of payment as "Pay on Service" and see the info message in review application and property type screen.				UAT	Windows
FSM/Citizen/04	Citizen	Citizen Flow	Check whether Citizen is able to skip the payment preference screen_English.	Functional	107-FSM-2022-02-23-005237	Login as Citizen with English language. Citizen enters the OTP. They should be able to select the payment preference screen. Citizen is able to skip the payment Preference screen and verify that post-service workflow is applied to the application. Citizen should read the info based on the payment type selected in the first screen and the other screens (review application and property type) as mentioned in SAN-842.	Citizen is able to skip the payment preference screen and see info message in the review application and property type screen applied for the post-service flow.			Reviewed	Citizen is able to skip the payment preference screen and see the info message in the review application. Property type screen should also be applied for the post-service flow.				UAT	Windows
FSM/Citizen/05	Citizen	Citizen Flow	Check whether Citizen is able to see the choice of payment as "Pay Now" or "Pay on Service"_Hindi.	Functional		Login as Citizen with Hindi language. Citizen enters the OTP. They should be able to select the payment preference screen. Citizen is able to see the choice of payment as "Pay Now" or "Pay on Service." Citizen is able to see the info message about when to make the payment as mentioned in SAN-842.	Citizen is able to see the choice of payment as "Pay Now" or "Pay on Service" with the info message.			Reviewed	Citizen is able to see the choice of payment as "Pay Now" or "Pay on Service" with the info message.				UAT	Windows
FSM/Citizen/06	Citizen	Citizen Flow	Check whether Citizen is able to select the choice of payment as "Pay Now"_Hindi.	Functional		Login as Citizen with Hindi language. Citizen enters the OTP. They should be able to select the payment preference screen. Citizen is able to select the choice of payment as "Pay Now" and verify pre-service workflow should be applied to the application. Citizen should read the info based on the payment type selected in the first screen and the other screens (review application and property type) as mentioned in SAN-842.	Citizen is able to select the choice of payment as "Pay Now" and see the info message in the review application and property type screen.			Reviewed	Citizen is able to select the choice of payment as "Pay Now" and o see the info message in review application and property type screen.
FSM/Citizen/07	Citizen	Citizen Flow	Check whether Citizen is able to select the choice of payment as "Pay on Service" _Hindi.	Functional		Login as Citizen with Hindi language. Citizen enters the OTP. They should be able to select the payment preference screen. Citizen is able to select the choice of payment as "Pay on Service" and verify that post-service workflow is applied to the application. Citizen should read the info based on the payment type selected in the first screen and the other screens (review application and property type) as mentioned in SAN-842.	Citizen is able to select the Choice of payment as "Pay on Service" and see the info message in the review application and property type screen.	Done	Done	Reviewed	Citizen is able to select the choice of payment as "Pay on Service" and see the info message in the review application and property type screen.	PASSED
FSM/Citizen/08	Citizen	Citizen Flow	Check whether Citizen is able to skip the payment preference screen_Hindi.	Functional	02/03 107-FSM-2022-03-02-005257	Login as Citizen with Hindi language. Citizen enters the OTP. They should be able to select the payment preference screen. Citizen is able to skip the payment preference screen and verify that the post-service workflow is applied to the application. Citizen should read the info based on the payment type selected in the first screen and the other screens (review application and property type) as mentioned in SAN-842.	Citizen is able to skip the payment preference screen and see the info message in the review application and property type screen applied for the post-service flow.	Done	Done	Reviewed	Citizen is able to skip the payment preference screen and see the info message in the review application as well as the property type screen applied for post service flow	PASSED
								Done	Done			PASSED
		FSM_CREATOR_EMP	https://digit-discuss.atlassian.net/browse/SAN-840					Done	Done			PASSED
FSM/FSM_CREATOR_EMP_01	FSM_CREATOR_EMP	FSM_CREATOR_EMP	Check whether FSM_CREATOR can create an application request with property type institutional, with capacity of vehicle as 5000 litres and number os trips 3 - the auto calculated amount should be: 2400 * 3 = Rs.7200/- -- ENGLISH. 03/03 Only editor can edit the number of trips as part of sprint 4 story; the creator part is covered in sprint 5 story SAN-904.	Functional	04/03 citizen - 107-FSM-2022-03-02-005253	Login as citizen/creator and create an application. Login as editor and check if you are able to edit the application. Check if the number of trips is editable by selecting INSTITUTIONAL. Total price calculated should be the number of trips * price for each price.	Calculated amount should display:2 400*3 = Rs.7200/-				The calculated amount should display: 2400*3 = Rs.7200/-
FSM/FSM_CREATOR_EMP_02	FSM_CREATOR_EMP	FSM_CREATOR_EMP	Check whether FSM_CREATOR can create an application request with property type commercial, with capacity as 1000 and number of trips 1 - the auto calculated amount should be: 1000*1 = Rs.1000/- -- ENGLISH.	Functional	04/03 citizen - 107-FSM-2022-03-02-005253	Login as FSM_CREATOR_EMP. FSM_CREATOR should enter login ID and password, choosing city as Amritsar. Navigate to the application creation page. Enter all the required fields, make sure to select COMMERCIAL, with capacity as 1000 and number of trips as 1. Auto Calculated amount should display: 1000*1 = Rs.1000/-	The calculated amount should be: 1000*1 = Rs.1000/-	Done	Done		The calculated amount should be: 1000*1 = Rs.1000/-	PASSED
FSM/FSM_CREATOR_EMP_03	FSM_CREATOR_EMP	FSM_CREATOR_EMP	Check whether FSM_CREATOR can create an application request with property type residential, with capacity of vehicle as 5000 litres with slum data and number os trips 3 - the auto calculated amount should be: 1500 * 3 = Rs.4500/- -- ENGLISH.	Functional	04/03 citizen - 107-FSM-2022-03-02-005253	Login as FSM_CREATOR_EMP. FSM_CREATOR should enter login ID and password, choosing city as Amritsar. Navigate to the application creation page. Enter all the required fields, make sure to select RESIDENTIAL, with capacity of vehicle as 5000 litres with slum data and number of trips as 3. Auto calculated amount should be: 1500*3 = Rs.4500/-	The calculated amount should be: 1500*3 = Rs.4500/-	Done	Done		The calculated amount should be: 1500*3 = Rs.4500/-	PASSED
FSM/FSM_CREATOR_EMP_04	FSM_CREATOR_EMP	FSM_CREATOR_EMP	Check whether FSM_CREATOR can create an application request with property type institutional, with capacity of vehicle as 5000 litres and number os trips 3 - the auto calculated amount should be: 2400 * 3 = Rs.7200/- -- HINDI.	Functional	04/03 citizen - 107-FSM-2022-03-02-005253	Login as FSM_CREATOR_EMP. FSM_CREATOR should enter login ID and password, choosing city as Amritsar. Navigate to the application creation page. Enter all the required fields, make sure to select INSTITUTIONAL, with capacity of vehicle as 5000 litres and number of trips as 3. Auto calculated amount should display: 2400*3 = Rs.7200/-	The calculated amount should display: 2400*3 = Rs.7200/-	Done	Done		The calculated amount should display: 2400*3 = Rs.7200/-	PASSED
FSM/FSM_CREATOR_EMP_05	FSM_CREATOR_EMP	FSM_CREATOR_EMP	Check whether FSM_CREATOR can create an application request with property type commercial, with capacity as 1000 and number of trips 1 - the auto calculated amount should be: 1000*1 = Rs.1000/- -- HINDI.	Functional	04/03 citizen - 107-FSM-2022-03-02-005253	Login as FSM_CREATOR_EMP. FSM_CREATOR should enter login ID and password, choosing city as Amritsar. Navigate to the application creation page. Enter all the required fields, make sure to select COMMERCIAL, with capacity as 1000 and number of trips as 1. Auto calculated amount should display: 1000*1 = Rs.1000/-	The calculated amount should be: 1000*1 = Rs.1000/-	Done	Done		The calculated amount should be: 1000*1 = Rs.1000/-	PASSED
FSM/FSM_CREATOR_EMP_06	FSM_CREATOR_EMP	FSM_CREATOR_EMP	Check whether FSM_CREATOR can create an application request with property type residential, with capacity of vehicle as 5000 litres with slum data and number os trips 3 - the auto calculated amount should be: 1500 * 3 = Rs.4500/- -- HINDI.	Functional	04/03 citizen - 107-FSM-2022-03-02-005253	Login as FSM_CREATOR_EMP. FSM_CREATOR should enter login ID and password, choosing city as Amritsar. Navigate to the application creation page. Enter all the required fields, make sure to select RESIDENTIAL, with capacity of vehicle as 5000 litres, with slum data and number of trips as 3. Auto calculated amount should be: 1500*3 = Rs.4500/-	The calculated amount should be: 1500*3 = Rs.4500/-	Done	Done		The calculated amount should be: 1500*3 = Rs.4500/-	PASSED
		ULB_EMPLOYEE(FSM_CREATOR_EMP)	https://digit-discuss.atlassian.net/browse/SAN-853
ULB_EMPLOYEE_01	FSM_CREATOR_EMP	ULB_EMPLOYEE	Check whether entering number of vehicle trips should be a mandate field for a ULB employee.	Functional		Login as FSM_CREATOR_EMP(ULB Employee). Fill all the necessary information. Check whether the number of vehicle trips should be a mandatory field.	Entering the number of vehicle trips should be a mandatory field for a ULB employee.	Done	Done		Entering the number of vehicle trips should be a mandatory field for a ULB employee.	PASSED
ULB_EMPLOYEE_02	FSM_CREATOR_EMP	ULB_EMPLOYEE	Check whether one is able to edit the number of trips and vehicle even after modifying the first time.	Functional	04/03 107-FSM-2022-03-04-005271	Login as FSM_CREATOR_EMP(ULB Employee). Fill all the necessary information. Check whether the number of vehicle trips should be a mandatory field. Submit the application. Go the application created in the previous step. Check whether a ULB employee is able to edit the number of trips and vehicle even after modifying the first time.	ULB employee should be able to edit the number of trips and vehicle even after modifying the first time.	Done	Done		ULB employee should be able to edit the number of trips and vehicle even after modifying the first time.	PASSED
FSM_DSO_03	FSM_CREATOR_EMP and FSM_DSO	ULB Employee and FSM_DSO	Check whether DSO operator is able to override the number of trips entered by a ULB operator.	Functional		Login as FSM_CREATOR_EMP(ULB Employee). Fill all the necessary information. Check whether the number of vehicle trips should be a mandatory field. Submit the application. Login with FSM_DSO and search for the application created above. Check whether a DSO operator is able to override the number of trips entered by a ULB operator.	DSO operator should able to override the number of trips entered by a ULB operator.	Done	Done		DSO operator should able to override the number of trips entered by a ULB operator.	PASSED
CITIZEN_04	FSM_CREATOR_EMP and Citizen	ULB Employee and Citizen	Check whether one gets a payment prompt on the number of trips.	Functional	Check whether citizen should receive the prompt after the complete workflow or whether after FSM creating a apliation	Login as FSM_CREATOR_EMP(ULB Employee). Fill all the necessary information by providing the correct citizen mobile number and city. Check whether the number of vehicle trips should be a mandatory field. Submit the application. Go the application created in the previous step. Check whether ULB employee is able to edit the number of trips and vehicle even after modifying the first time. Login as a citizen and complete the payment, check if he/she is prompted to make the payment based on the number of trips selected in the above step.	Check whether one receives a payment prompt on the number of trips.	Done	Done		Check whether one receives a payment prompt on the number of trips.	PASSED
FSTPO_05	FSM_CREATOR_EMP Citizen FSM_DSO FSM_EMP_FSTP	FSTPO	Check whether one gets a payment prompt on the number of trips.	Functional	Check if you need to go through the complete work flow, starting from FSM_EMP creating app, citizen making payment, DSO assignment, FSTPO completing the trip.	Login as FSM_CREATOR_EMP (ULB Employee). Fill all the necessary information by providing the correct citizen mobile number and city. Check whether the number of vehicle trips should be a mandatory field. Submit the application. Go the application created in the previous step. Check whether ULB employee is able to edit the number of trips and vehicle even after modifying the first time. Login as a citizen and complete the payment, check if he/she is prompted to make the payment based on the number of trips selected in the above step. Login as DSO operator and assign the vehicle. Once the workflow is completed, login as FSM_EMP_FSTPO. Check whether FSM_EMP_FSTPO has the number of cards generated for each disposal based on the number of trips entered.	Check whether one receives a payment prompt on the number of trips.	Done	Done		Check whether one receives a payment prompt on the number of trips.	PASSED
		ULB_EMPLOYEE(FSM_CREATOR_EMP)	https://digit-discuss.atlassian.net/browse/SAN-844
DSO_01	FSM_DSO	CITIZEN FSM_EDITOR FSM_DSO	Check whether entering the number of vehicle trips is a mandatory field for a DSO-- DSO login.	Functional 107-FSM-2022-02-23-005238	Create an application with Citizen login, Edit with fSM_EDITOR, Login with FSM_DSO and check for the mandatory field.	Login as Citizen. Fill all the necessary information. Edit the application using FSM_EDITOR, login and complete from his/her end to move to the next step. Login with FSM_DSO and check whether number of vehicle trips is a mandatory field. Submit the application.	Entering the number of vehicle trips should be a mandatory field for a DSO.				Entering the number of vehicle trips should be a mandatory field for a DSO.	PASSED
DSO_02	FSM_DSO	CITIZEN FSM_EDITOR FSM_DSO	Check whether DSO is able to edit the vehicle even after entering.	Functional	Create an application with Citizen login, Edit with fSM_EDITOR, Login with FSM_DSO and check for the mandatory field.	Login as Citizen. Fill all the necessary information. Edit the application using FSM_EDITOR, login and complete from his/her end to move to the next step. Login with FSM_DSO and check whether he/she is able to edit the vehicle even after entering. Submit the application.	DSO should be able to edit the vehicle even after entering.				DSO should be able to edit the vehicle even after entering
DSO_03	FSM_DSO	CITIZEN FSM_EDITOR FSM_DSO	Check whether DSO operator is able to override the number of trips entered by a ULB operator.	Functional	Create an application with Citizen login, Edit with fSM_EDITOR, Login with FSM_DSO and check for the mandatory field.	Login as Citizen. Fill the necessary information. Edit the application using FSM_EDITOR login and complete from his/her end to move to the next step. Login with FSM_DSO and check whether DSO operator is able to override the number of trips entered by ULB operator. Submit the application.	DSO operator should be able to override the number of trips entered by a ULB operator.	Done	Done		DSO operator should be able to override the number of trips entered by a ULB operator.	PASSED
CITIZEN_DSO_04	CITIZEN	CITIZEN FSM_EDITOR FSM_DSO	Check whether Citizen receives a prompt on the number of trips.	Functional	Create an application with Citizen login, Edit with fSM_EDITOR, Login with FSM_DSO and a citizen receiving the prompt on the number of trips.	Login as Citizen. Fill all the necessary information. Edit the application using FSM_EDITOR login and complete from his/her end to move to the next step. Login with FSM_DSO and enter the necessary information, including the number of vehicle trips. Submit the application. Check whether a citizen receives a prompt on the number of trips.	Citizen must receive a prompt on the number of trips.	Done	Done		Citizen must receive a prompt on the number of trips.	PASSED
DSO_FSTPO_05	FSM_DSO FSTPO	CITIZEN FSM_EDITOR FSM_DSO FSTPO	Check whether DSO can send a trigger for the FSTP application to create a number of cards based on the number of trips.	Functional	Create an application with Citizen login, Edit with fSM_EDITOR, Login with FSM_DSO. A trigger is sent to for the FSTP application to create a number of cards based on the number of trips.	Login as Citizen. Fill all the necessary information. Edit the application using FSM_EDITOR login and complete from his/her end to move to the next step. Login with FSM_DSO and enter the necessary information, including the number of vehicle trips. Submit the application. Login as FSTPO. Check whether FSTPO receives a trigger to create a number of cards based on the number of trips.	DSO sends a trigger for the FSTP application to create a number of cards based on the number of trips.	Done	Done		DSO sends a trigger for the FSTP application to create a number of cards based on the number of trips.	PASSED
DSO_FSTPO_CITIZEN_06	FSM_DSO FSTPO CITIZEN	CITIZEN FSM_EDITOR FSM_DSO FSTPO	Check whether CITIZEN receives a trigger SMS and app notification to make the payment, and the status is marked as payment pending.	Functional	Create an application with Citizen login, Edit with fSM_EDITOR, Login with FSM_DSO and a trigger is sent to for the FSTP application to create number of cards based on the number of trips. A citizen should receive a trigger with SMS and app notification, and the status should be updated to the payment pending in the citizen login.	Login as Citizen. Fill all the necessary information. Edit the application using FSM_EDITOR login and complete from his/her end to move to the next step. Login with FSM_DSO and enter the necessary information, including the number of vehicle trips. Submit the application. Login as FSTPO. Check whether FSTPO receives a trigger to create a number of cards based on the number of trips. Login with Citizen. Check if a citizen receives an SMS and app notification stating that he/she should make the payment, and that the status of the application is changed to payment pending.	Triggers SMS and app notification for a citizen to make the payment. Status in the inbox is changed to payment pending.	Done	Done		Tiggers SMS and app notification for a citizen to make the payment. Status in the inbox is changed to payment pending.	PASSED
DSO_07	DSO	CITIZEN FSM_EDITOR FSM_DSO FSTPO	Check whether the back button will go to the previous application summary screen, where the DSO can decline a request or assign a vehicle. Check if by clicking take action in the application summary → complete request, the below screen is shown where all the information is pre-filled and the DSO has the option to edit and complete a request.	Functional	Create an application with Citizen login, Edit with fSM_EDITOR, Login with FSM_DSO and go until assigning the vehicle. Then go to next page.	Login as Citizen. Fill all the necessary information. Edit the application using FSM_EDITOR login and complete from his/her end to move to the next step. Login with FSM_DSO and enter the necessary information, including the number of vehicle trips. Before submitting the application, click on the back button and check if it goes to the previous application summary screen where the DSO can decline a request or assign a vehicle. Again, by clicking take action in the application summary → Complete request, the below screen is shown where all the information is pre-filled and the DSO has the option to edit and complete the request.	The back button must go to the previous application summary screen where the DSO can decline a request or assign a vehicle. Again, by clicking take action in the application summary → Complete request, the below screen is shown where all the information is pre-filled and the DSO has the option to edit and complete the request.	Done	Done		The back button must go to the previous application summary screen where the DSO can decline a request or assign a vehicle, Again by clicking take action in the application summary → complete request, the below screen is shown where all the information is pre-filled and the DSO has the option to edit and complete a request	PASSED
								Done	Done			PASSED
		FSM_EDITOR_EMP and FSM_EMP_FSTPO	https://digit-discuss.atlassian.net/browse/SAN-803					Done	Done			PASSED
FSM_EDITOR_Waiting_For_Dsiposal_Disposed_01	FSM_EDITOR_EMP	CITIZEN FSM_EDITOR DSO login FSM_FSTPO	Check if the following status is updated: 1. Waiting for disposal 2. Disposed 3. Customer Feedback Rating-- Existing functionality --ENGLISH	Functional		Login as FSM_CREATOR. Create an application and submit. Login as FSM_EDITOR, go to the inbox and look for the application created above. Complete the DSO assignment process. Login with DSO and complete the DSO process. Now the application status should be waiting for disposal since FSTPO is yet to act on this. Login with FSM_EDITOR, go to the inbox, and check the status of the application. It should show as "Waiting for Disposal." Now login with FSM_FSTPO and complete the application process. Login with FSM_EDITOR and check the status under inbox. It should show as "Disposed." Once the status is changed to disposed, verify if the status is changed to "customer feedback pending" on the application--existing functionality.	FSM_EDITOR The following should be updated accordingly: 1. Waiting for disposal 2. Disposed 3. Customer feedback rating-- existing functionality.	Done	Done		FSM_EDITOR The following should be updated accordingly: 1. Waiting for disposal 2. Disposed 3. Customer feedback rating-- existing functionality	PASSED
FSM_EDITOR_SLA_for_Waiting_For_Dsiposal_Disposed_02	FSM_EDITOR_EMP	CITIZEN FSM_EDITOR DSO login FSM_FSTPO	Check the SLA column to see if the following status is present as - (No value) 1. Waiting for disposal 2. Disposed --ENGLISH	Functional		Login as a FSM_CREATOR. Create an application and submit. Login as FSM_EDITOR, go to the inbox and look for the application created above. Complete the DSO assignment process. Login with DSO and complete the DSO process. The application status should be waiting for disposal since FSTPO is yet to act on this. Login with FSM_EDITOR, go to inbox and check if the SLA status is displayed as - (no value) for app status as "Waiting for Disposal." Now login with FSM_FSTPO and complete the application process. Login with FSM_EDITOR and check the status under inbox. The SLA status should be displayed as - (no value) for application status as "disposed"	FSM_EDITOR SLA should be displayed as - for both the status of application.	Done	Done		FSM_EDITOR SLA should be displayed as - for both the status of application.	PASSED
FSM_EMP_FSTPO_Waiting_For_Dsiposal_Disposed_03	FSM_EMP_FSTPO	CITIZEN FSM_EDITOR DSO login FSM_FSTPO	Check if the following status is updated: 1. Waiting for disposal 2. Disposed 3. Customer Feedback Rating-- Existing functionality --ENGLISH	Functional		Login as a FSM_CREATOR. Create an application and submit. Login as FSM_EMP_FSTPO, go to the inbox and look for the application created above. Complete the DSO assignment process. Login with DSO and complete the DSO process. The application status should be waiting for disposal since FSTPO is yet to act on this. Login with FSM_EMP_FSTPO, go to the inbox and check the status of the application. It should show as "Waiting for Disposal." Now login with FSM_FSTPO and complete the application process. Login with FSM_EMP_FSTPO and check the status under inbox. It should show as "Disposed." Once the status is changed to disposed, verify if the status is changed to "customer feedback pending" on the application--existing functionality.	FSM_EMP_FSTPO The following should be updated accordingly: 1. Waiting for disposal 2. Disposed 3. Customer feedback rating-- existing functionality.	Done	Done		FSM_EMP_FSTPO All the 3 below status should be updated accordingly 1. Waiting for disposal 2. Disposed 3. Customer Fedback Rating-- Existing functionality	PASSED
FSM_EMP_FSTPO_SLA_for_Waiting_For_Dsiposal_Disposed_04	FSM_EMP_FSTPO	CITIZEN FSM_EDITOR DSO login FSM_FSTPO	Check the SLA column to see if the following status is present as - (No value) 1. Waiting for disposal 2. Disposed --ENGLISH	Functional		Login as FSM_CREATOR. Create an application and submit. Login as FSM_EMP_FSTPO, go to inbox and look for the application created above. Complete the DSO assignment process. Login with DSO and complete the DSO process. The application status should be waiting for disposal since FSTPO is yet to act on this. Login with FSM_EMP_FSTPO, go to the inbox and check the SLA status of the application vehicle trip status. "Waiting for Disposal" should be displayed as - (no value). Now login with FSM_FSTPO and complete the application process. Login with FSM_EMP_FSTPO and check the status under inbox. The SLA status should be displayed as - (no value) for application status as "disposed."	FSM_EMP_FSTPO SLA should be displayed as - for both the status of application.	Done	Done		FSM_EMP_FSTPO SLA should be displayed as - for both the status of application	PASSED
FSM_EDITOR_Waiting_For_Dsiposal_Disposed_HINDI_05	FSM_EDITOR_EMP	CITIZEN FSM_EDITOR DSO login FSM_FSTPO	Check whether the following statuses are updated: 1. Waiting for disposal 2. Disposed 3. Customer feedback rating-- existing functionality --HINDI	Functional		Login as a FSM_CREATOR. Create an application and submit. Login as FSM_EDITOR, go to the inbox and look for the application created above. Complete the DSO assignment process. Login with DSO and complete the DSO process. The application status should be waiting for disposal since FSTPO is yet to act on this. Login with FSM_EDITOR, go to the inbox and check the status of the application. It should show as "Waiting for Disposal." Now login with FSM_FSTPO and complete the application process. Login with FSM_EDITOR and check the status under inbox. It should show as "Disposed." Once the status is changed to disposed, verify if the status is changed to "customer feedback pending" on the application--existing functionality.	FSM_EDITOR The following should be updated accordingly: 1. Waiting for disposal 2. Disposed 3. Customer feedback rating-- existing functionality.	Done	Done		FSM_EDITOR All the 3 below status should be updated accordingly 1. Waiting for disposal 2. Disposed 3. Customer Fedback Rating-- Existing functionality	PASSED
FSM_EDITOR_SLA_for_Waiting_For_Dsiposal_Disposed_HINDI_06	FSM_EDITOR_EMP	CITIZEN FSM_EDITOR DSO login FSM_FSTPO	Check for SLA column to see if below status is present as - (No value) 1. Waiting for disposal 2. Disposed --HINDI	Functional		Login as FSM_CREATOR. Create an application and submit. Login as FSM_EDITOR, go to inbox and look for the application created above. Complete the DSO assignment process. Login with DSO and complete DSO process. The application status should be waiting for disposal since FSTPO is yet to act on this. Login with FSM_EDITOR, go to the inbox and check the SLA status. It should be displayed as - (no value) for app status as "Waiting for Disposal." Now login with FSM_FSTPO and complete the application process. Login with FSM_EDITOR and check the status under inbox. The SLA status should be displayed as - (no value) for application status as "disposed."	FSM_EDITOR SLA should be displayed as - for both the status of the application.	Done	Done		FSM_EDITOR SLA should be displayed as - for both the status of application	PASSED
FSM_EMP_FSTPO_Waiting_For_Dsiposal_Disposed_HINDI_07	FSM_EMP_FSTPO	CITIZEN FSM_EDITOR DSO login FSM_FSTPO	Check whether below status is updated: 1. Waiting for disposal 2. Disposed 3. Customer Fedback Rating-- Existing functionality --HINDI	Functional		Login as a FSM_CREATOR. Create an application and submit. Login as FSM_EMP_FSTPO, go to the inbox and look for the application created above. Complete the DSO assignment process. Login with DSO and complete the DSO process. The application status should be waiting for disposal since FSTPO is yet to act on this. Login with FSM_EMP_FSTPO, go to the inbox and check the status of the application. It should show as "Waiting for Disposal." Login with FSM_FSTPO and complete the application process. Now login with FSM_EMP_FSTPO and check the status under inbox. It should show as "Disposed." Once the status is changed to disposed, verify if the status is changed to "customer feedback pending" on the application--existing functionality.	FSM_EMP_FSTPO The following should be updated accordingly: 1. Waiting for disposal 2. Disposed 3. Customer feedback rating-- existing functionality	Done	Done		FSM_EMP_FSTPO The following should be updated accordingly: 1. Waiting for disposal 2. Disposed 3. Customer feedback rating-- existing functionality	PASSED
FSM_EMP_FSTPO_SLA_for_Waiting_For_Dsiposal_Disposed_HINDI_08	FSM_EMP_FSTPO	CITIZEN FSM_EDITOR DSO login FSM_FSTPO	Check for the SLA column to see if the below status is present as - (No value) 1. Waiting for disposal 2. Disposed --HINDI	Functional		Login as FSM_CREATOR. Create an application and submit. Login as FSM_EMP_FSTPO, go to the inbox and look for the application created above. Complete the DSO assignment process. Login with DSO and complete the DSO process. Now the application status should be waiting for disposal since FSTPO is yet to act on this. Login with FSM_EMP_FSTPO, go to inbox and check that the SLA status of the application vehicle trip status as "Waiting for Disposal" should be displayed as - (no value). Now login with FSM_FSTPO and complete the application process. Login with FSM_EMP_FSTPO and check the status under inbox. SLA status should be displayed as - (no value) for application status as "disposed."	FSM_EMP_FSTPO SLA should be displayed as - for both the status of application.	Done	Done		FSM_EMP_FSTPO SLA should be displayed as - for both the status of application.	PASSED
FSM/Emp/03	Employee flow		Validate if the "Waiting for disposal" application status is added in the filter _English.	Functional	Login as a ULB Employee on the mSeva portal with English language. Navigate to FSM. Go to the employee inbox. Validate that the "Waiting for disposal" application status is added in the filter. Validate "Waiting for disposal" under the “Application Status” and show “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Waiting for disposal" filter. User is able to see the "Waiting for disposal" under “Application Status” and “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on basis of the "Waiting for disposal" filter. User is able to see "Waiting for disposal" under “Application Status” and “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	Done	Done		User should be able to filter out the application on the basis of the "Waiting for disposal" filter. User is able to see "Waiting for disposal" under the “Application Status” and “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	PASSED		UAT	Windows	Google Chrome
FSM/Emp/04	Employee flow		Validate if the "Disposed" application status is added in the filter_English.	Functional	Login as a ULB Employee on the mSeva portal with English language. Navigate to FSM. Go to the employee inbox. Validate that the "Disposed" application status is added in the filter. Validate "Disposed" under “Application Status” and show “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Disposed" filter. User is able to see"Disposed" under the “Application Status” and “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on basis of the "Disposed" filter. User is able to see the "Disposed" under “Application Status” and “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.				User should be able to filter out the the application on the basis of the "Disposed" filter. User is able to see "Disposed" under the “Application Status” and see “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	PASSED		UAT	Windows	Google Chrome
FSM/Emp/05	Employee flow		Validate if the "Citizen Feedback Pending" application status is added in the filter _English.	Functional	Login as a ULB Employee on the mSeva portal with English language. Navigate to FSM. Go to the employee inbox. Validate that the "Citizen Feedback Pending" application status is added in the filter. Validate "Citizen Feedback Pending" under the “Application Status” and show “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Citizen Feedback Pending" filter. User is able to show "Citizen Feedback Pending" under the “Application Status” and see “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Citizen Feedback Pending" filter. User is able to show "Citizen Feedback Pending" under the “Application Status” and see “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.				User should be able to filter out the application on the basis of the "Citizen Feedback Pending" filter. User is able to show "Citizen Feedback Pending" under the “Application Status” and see “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	PASSED		UAT	Windows	Google Chrome
FSM/Emp/06	Employee flow		Validate if Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status are present in the filter_English.	Functional	Login as a ULB Employee on the mSeva portal with English language. Navigate to FSM. Go to the employee inbox. Validate Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status are present in the filter. Validate Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status under the “Application Status” and show “num of days” under “SLA Days Remaining.”	User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in the filter column. User is able to see the above status under the “Application Status” and “num of days” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in the filter column. User is able to see the above status under “Application Status” and “num of days” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	Done	Done		User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in the filter column. User is able to see the above status under “Application Status” and “num of days” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	PASSED		UAT	Windows	Google Chrome
FSM/Emp/07	Employee flow		Validate if the "Waiting for disposal" application status is added in the filter_Hindi.	Functional	Login as a ULB Employee on the mSeva portal with Hindi language. Navigate to FSM. Go to the employee inbox. Validate that the "Waiting for disposal" application status is added in the filter. Validate "Waiting for disposal" under the “Application Status” and show “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Waiting for disposal" filter. User is able to see "Waiting for disposal" under “Application Status” and “-” under “SLA Days Remaining.”	User should be able to filter out the the application on basis of the "Waiting for disposal" filter. User is able to see "Waiting for disposal" under “Application Status” and “-” under “SLA Days Remaining.”	Done	Done		User should be able to filter out the application on the basis of the "Waiting for disposal" filter. User is able to see "Waiting for disposal" under the “Application Status” and “-” under “SLA Days Remaining.”	PASSED		UAT	Windows	Google Chrome
FSM/Emp/08	Employee flow		Validate if the "Disposed" application status is added in the filter_Hindi.	Functional	Login as a ULB Employee on the mSeva portal with Hindi language. Navigate to FSM. Go to the employee inbox. Validate that the "Disposed" application status is added in the filter. Validate "Disposed" under “Application Status” and show “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	User should be able to Filter out the application on the basis of "Disposed" filter. User is able to see "Disposed" under “Application Status” and “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	User should be able to Filter out the application on the basis of "Disposed" filter. User is able to see "Disposed" under “Application Status” and “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	Done	Done		User should be able to filter out the application on the basis of the "Disposed" filter. User is able to see "Disposed" under the “Application Status” and “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	PASSED		UAT	Windows	Google Chrome
FSM/Emp/09	Employee flow		Validate if the "Citizen Feedback Pending" application status is added in the filter_Hindi.	Functional	Login as a ULB Employee on the mSeva Portal with Hindi language. Navigate to FSM. Go to the employee inbox. Validate that the "Citizen Feedback Pending" application status is added in the filter. Validate "Citizen Feedback Pending" under “Application Status” and show “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on application.	User should be able to filter out the application on the basis of the "Citizen Feedback Pending" filter. User is able to show "Citizen Feedback Pending" under “Application Status” and see “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	User should be able to filter out the application on the basis of the "Citizen Feedback Pending" filter. User is able to show "Citizen Feedback Pending" under “Application Status” and see “-” under “SLA Days Remaining.” The status should also reflect on the application timeline when a user clicks on the application.	Done	Done		User should be able to filter out the application on basis of "Citizen Feedback Pending" filter. User is able to show "Citizen Feedback Pending" under the “Application Status” and see “-” under “SLA Days Remaining.” Status should also reflect on the application timeline when a user clicks on the application.	PASSED		UAT	Windows	Google Chrome
FSM/Emp/10	Employee flow		Validate if Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status are present in the filter_Hindi.	Functional	Login as a ULB employee on the mSeva portal with Hindi language. Navigate to FSM. Go to the employee inbox. Validate Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status are present in the filter. Validate "Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status under “Application Status” and show “num of days” under “SLA Days Remaining.”	User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in the filter column. User is able to see the above status under “Application Status” and see “num of days” under “SLA Days Remaining.”	User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in the filter column. User is able to see the above status under “Application Status” and “num of days” under “SLA Days Remaining.”	Done	Done		User should be able to see Application Created, Pending DSO Assignment, Pending for Payment, Pending for DSO Approval, DSO Rejected, DSO InProgress application status in the filter column. User is able to see above status under “Application Status” and “num of days” under “SLA Days Remaining.”	PASSED		UAT	Windows	Google Chrome
		All Roles	https://digit-discuss.atlassian.net/browse/SAN-843
CITIZEN_01	CITIZEN flow	Make sure to test all workflows mentioned in the JIRA	Check whether Citizen is able to make payment at anytime from the time DSO generates payment until they mark it as Request Complete-- DSO generates payment.	Functional- UI	Login as a CITIZEN. Create an application by choosing pre/post pay. Submit the application. Complete the flow from fSM_EDITOR by taking the necessary actions. Login as DSO and generate the payment. Login as citizen and check if you are able to make payment.	Citizen should be able to make the payment.	Citizen should be able to make the payment.	Done	Done		Citizen should be able to make the payment.	PASSED		UAT	Windows	Google Chrome
CITIZEN_02	CITIZEN flow	Make sure to test all workflows mentioned in the JIRA	Check whether Citizen is able to make the payment at anytime from the time DSO generates payment until they mark it as request complete--DSO completes request.	Functional- UI	Login as a CITIZEN. Create an application choosing pre/post-pay. Submit the application. Complete the flow from fSM_EDITOR by taking the necessary actions. Login as DSO and generate the payment. DSO completes the request. Login as citizen and check if you are able to make the payment. Note: We are checking if a citizen is able to make the payment even after DSO completes the request.	Citizen should be able to make the payment. Note: We are checking if a citizen is able to make the payment even after the DSO completes the request.	Citizen should be able to make the payment. Note: We are checking if a citizen is able to make the payment even after the DSO completes the request.				Citizen should be able to make the payment. Note: We are checking if a citizen is able to make the payment even after DSO completes the request.			UAT	Windows	Google Chrome
CITIZEN_PRE_PAY_03	CITIZEN flow: Pre-pay flow	Make sure to test all workflows mentioned in the JIRA.	Check whether "Citizen should be able to select which payment mode they want to have."-- PRE PAY.	Functional- UI	Login as a CITIZEN. Create an application using pre-pay.	Citizen should be able to choose the choice of payment.	Citizen should be able to choose the choice of payment.				Citizen should be able to choose the choice of payment.			UAT	Windows	Google Chrome
CITIZEN_POST_PAY_04	CITIZEN flow: Post-pay flow	Make sure to test all workflows mentioned in the JIRA.	Check whether "Citizen should be able to select which payment mode they want to have." -- POST PAY.	Functional- UI	Login as a CITIZEN. Create an application using post-pay	Citizen should be able to choose the choice of payment.	Citizen should be able to choose the choice of payment.	Done	Done		Citizen should be able to choose the choice of payment.	PASSED		UAT	Windows	Google Chrome
FSTPO_REJECTS_05	ULB EMP and FSTPO flow		Check if FSTP rejects, it should reflect on the ULB employees' timeline.	Functional- UI	Login as FSM_EMP_CREATO and create an application. Login as FSM_COLLECTOR and collect the payment. Login as FSM_EDITOR and perform the necessary actions. Login as DSO and accept the application. Login as FSTPO and reject the application. Login as FSM_EMP and check if the application status is shown as REJECTED in the timeline.	Application status should be shown as REJECTED in EMP when FSTPO rejects the application.	Application status should be shown as REJECTED in EMP when FSTPO rejects the application.	Done	Done		Application status should be shown as REJECTED in EMP when FSTPO rejects the application.	PASSED		UAT	Windows	Google Chrome
								Done	Done			PASSED
		All Roles	https://digit-discuss.atlassian.net/browse/SAN-689
OWNER_ATTRIBUTE_VEHICLE_01		API TC	Check whether create and update vehicle information is available via API.		Check whether create and update vehicle information is available via API.	Check whether create and update vehicle information is available via API.	Check whether create and update vehicle information is available via API				Check whether create and update vehicle information is available via API.			UAT	Windows	Google Chrome
		All Roles	https://digit-discuss.atlassian.net/browse/SAN-616
vehicle_trip_status_01		API TC	Check whether employee inbox, for all roles, should have additional application statuses to filter by, as mentioned above.		Check from the inbox API for vehicle trip status.	Employee inbox, for all roles, should have additional application statuses to filter by as mentioned above.	Employee inbox, for all roles, should have additional application statuses to filter by as mentioned above.	Done	Done		Employee inbox, for all roles, should have additional application statuses to filter by as mentioned above.	PASSED		UAT	Windows	Google Chrome
vehicle_trip_status_02		API TC	Check whether application status and SLA days remaining column should show conditional values as mentioned above.		Check from the inbox API for vehicle trip status.	Application status and SLA days remaining column should show conditional values as mentioned above.	Application status and SLA days remaining column should show conditional values as mentioned above.	Done	Done		Application status and SLA days remaining column should show conditional values as mentioned above.	PASSED		UAT	Windows	Google Chrome
vehicle_trip_status_03		API TC	Check the current load time of the page and ensure the load time of the inbox page does not drop.		Check from the inbox API for vehicle trip status.	Report the current load time of the page and ensure that the load time of the inbox page does not drop.	Please report the current load time of the page and ensure the load time of the inbox page does not drop.	Done	Done		Please report the current load time of the page and ensure the load time of the inbox page does not drop.	PASSED		UAT	Windows	Google Chrome

​​​All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.