bobbyfengb1124 / italyrepo Goto Github PK

How to decipher the multiple violations from violation code field

For the input value from user key in, we need add validation for what user key in(such as charset, alphanumeric, string length) and add test case for it. Please refer to the sample we provide as reference.

1. is the image request API and Trajectory API synchronous or asynchronous?
2. if gateway can reach an OBU immediately, but it will take some time to upload the image, what information will be given to EBOS?
3. if gateway cannot reach an OBU immediately, what information will be given to EBOS?
4. if gateway try to reach an OBU but timeout, what information will be given to EBOS?

Column C – this column cannot be blank as it forms part of the TEST ID (column A). Suggest to put abbreviation of your function name, such as MNL for manual processing, IMG for image library and ERE for enforcement record enquiry (Just a propose for your reference).

Hi Chen Chen,

As the UI guideline indicated on page 9, section 3.1.1.3.1, the font size for button is 18px, it is not updated as meeting mentioned.
Pls help us to check for the latest guideline.
Thank you very much.

Thanks & Regards
Feng Bo

Column E – put ‘00’ for all test cases

unsuccessfulPaymentTransactionService.putEbosUnsuccessfulPaymentTransactionToDiscardQueue

Hi Chen Chen,

Could you also send us the ERP project page header footer?

unsuccessfulPaymentTransactionService.putEbosUnsuccessfulPaymentTransactionToDiscardQueue

Column G –Need to update and put in the relevant SDS clause. URAR clause and Sequence diagram number do not need to put in this column. Because we are doing mapping as below:
TS/FS/URAR <--> SDS <--> Test Cases.

Please make sure all of your SDS clause is covered by your test cases.

review the tables from EFE and sync

For some test cases, it is needed to split into different test cases to test different flow, happy-flow and unhappy flow. Such as trajectory data is available or trajectory data is not available. In this way, it is clear cut for the user when to pass/fail the test.

For the UAT test case, no need to mention DB field update as it is transparent to user. Such as in test case SST-ENF-EBOS-003, in the expected result step 5. “PROC_FLG_CD column in table ENF_MANL_VLD change to ‘KQ1’”. This step should be removed out.

BTW, has the naming convention for Subsystem ID been fixed?
Could you give us some sample Subsystem ID number?

fix it as per client

Column I- put existing records needed for this test case. No need to mention DB table and field as it is transparent to UAT user. For example, for test case SST-ENF-EBOS-0003, just put as “Manual queue record to be processed exists in database”.

unsuccessfulPaymentTransactionService.logAudit(temp);

Column F – where are the TS values defined in “Scenarios for Online Functions” tab?

There are test steps stated under Pre-Condition. These should go under “Method / Procedure” column. Such as in test case SST-ENF-EBOS=001, Method / Procedure column, the first step should be “login as normal RP user”.

Need to check by tomorrow

Good Morning Choon Muay,

Could you let us know currently ERP1 licence plate checksum checking is done by a piece of program or based on a look up table in the database?

unsuccessfulPaymentTransactionService.logAudit(temp);

Please split the test cases into 3 files. Each online function has its own test case file.

Column J- Where are the input parameters for this test case. If the input parameters have different combination, the TCond tab is needed. Please refer to the sample we provided.

add search criteria test case
add enforcement enquiry exception test case
add image library test case