PRIORITY: 1
TEST_TYPE: manual
APPROVED_QE:
INPUT:
- Make sure the feature is enabled. 2. Through WebUI, add few contacts (to the Address Book) that have Scan To Destinations associated to them. 3. Make sure couple of contacts also are added to the Scan Favorites (WebUI). 4. Through WebUI, enable and setup the Auxiliary Access Device (FDI). Steps to enable FDI at the device: 1) At the device WebUI, login as Administrator. 2) Go to the Properties tab -- Login/Permissions/Accounting -- Accounting Method. In the Accounting Method click the Edit button, then select Auxiliary Access Device from the dropdown. Click Save.
TESTCASE_HEADLINE: As an SA and I can manage Scan To ... jobs with FDI module.
FEATURE:
APPROVE_SE: blank
SPEC_VERSION: 1.0023
MFF: 2930 R611 - 4508 and 5476
TESTCASE_PLATFORM:
SPEC: FS 45.020 Foreign Device Interface
HISTORY:
CDATE: 1438596578
OUTPUT: Scan To ... jobs are run and managed on systems with FDI; the same as workflow scanning.
TESTCASE_STATE:
PROCESS:
RESOURCE_HW:
TC_WEIGHTAGE:
MDATE: 1438596578, 1532957144
APPROVED_SPAR:
SKILL_SET: intermediate
TESTCASE_SOURCE: feature_spec
APPROVE_QE: blank
TEST_CASE_TYPE: testcases
APPROVED_SE:
PLANNEDTIMESTAFF: 60
ATM_OWNER: USWU53873
AUTHOR: USWU53873
ASSOCIATED_TESTCASES:
LOE:
TRAINING:
ATM_REQLINK: B95A027A-6EAF-1014-80DB-EB12AA5362AD
MUSER: USWU53873, q4BVX0J1
GROUP: scan
SUB_FEATURE:
SPEC_TAG: [45.020.014] (FT-17266)
PROCEDURE:
- With FDI enabled and set the FDI device type to whatever is being used in the test through LUI->Machine Status->Tools->Accounting Settings->Accounting Mode->Auxiliary Access->Auxiliary Device Type. 2. Login into the LUI as Administrator and navigate to: Machine Status->Tools->Accounting Settings->Accounting Mode->Auxiliary Access->App Access and Accounting. Verify Scan To... and Workflow Scanning are selected/restricted among other services. Log out from Admin account. 3. Through LUI attempt a Network Scanning job and verify that the LUI Message informs the user to perform an action consistent with the device type in order to proceed with the Network Scanning job. (I.E. Insert Coin or Input PIN). 4. Go ahead and do as instructed in the LUI message. For Coin FDI device; insert Coin into the FDI device and make sure user can proceed with the Network Scanning job. Note: for scan jobs user is not being billed. 5. Perform one job where Confirmation sheet is printed after the scan job (with FDI enabled). 6. Perform the same test for Scan To... service (Scan to Destination) jobs as in step 2; 3; 4 and 5 of this test case. Velidate Scan to Destination jobs are handled the same way as Network Scanning jobs. 7. Go ahead and unrestrict the Scant To... service through LUI while leaving the Workflow Scanning restricted and FDI enabled. Log out from Admin account. Verify user is not restricted from using the Scan To... service. 8. Further FDI related testing shall be performed using already existing FDI test cases. Keep in mind; Scan To.. shall be handled the same as Workflow Scanning when FDI enabled.
RESOURCE_CONSUMEABLES:
ATM_LOCKED: 0
APPROVE_SPAR: blank
TESTCASE_PRODUCT: canyon, carroll, corvo, corrib, kiska, malawi, mystic, melody, muckross
ATM_ID: C0C58DDE-83F6-1014-AA13-9298F2E7BAC7
ATM_MCOMMENTS: Copied from "SAPT/Scanning/Address_Book/New_Address_Book/MMF_2930_R611_1d_Common_Address_Books_-/94061"., Renamed from "DPQA_Regression_SCANNING/Testcases/New_Address_Book/MMF_2930_R611_1d_Common_Address_Books_-/16014".
RESOURCE_MEDIA:
ATM_REQCOUNT: 1
TC_WORK_LOCATION_CAT: work_from_office_tc
DEVICE_CATEGORY: mfp
CONSTRAINTS_DAR: Imp_98 . Case 2- Existing TC's as MFP only. Add a New TC for SFP. Done By 0 dated on 00-01-1900
COMPETENCY: wfast_accounting
APTEST_TRACKING: yes
COMPLEXITY_OUTPUT_VALIDATION: non_outliers
AUTOMATION_CANDIDATE: yes
AUTOMATABLE: no
SRT_ANALYZATION: analyzed