Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

WEEKLY JOURNAL

Last Name First Name MI


Calising John Patrick B.

STI Campus Program Year Level Section


Balagtas BSIT 4th A

Host Company Department Assigned to

RT Lawrence Quality Assurance (IDA-RED)


Schedule (Date): Tuesday -Saturday (6:00am - 3:00pm) Number of Working Hours:
40

Weekly Accomplishments
The student trainee should give a summary of the tasks performed during the week and how it was accomplished.

NLP and DataAPI Nodes and Sub - nodes (Week5)

We're meticulously validating every NLP and Data API node and subnode in our test scripts. Our aim is to identify any
errors that may occur within each node and subnode. For instance, we thoroughly check for missing or differing values
specifically within AxesY. Additionally, we ensure the accuracy of SQL statements during our validation process. This
comprehensive approach helps us maintain the integrity and reliability of our systems. By conducting these checks, we
can confidently confirm the robustness of our NLP and Data API infrastructure.

Reviewed by: Date

OJT Supervisor Signature

Page 1 of 1
WEEKLY JOURNAL
Last Name First Name MI
Calising John Patrick B.

STI Campus Program Year Level Section


Balagtas BSIT 4th A

Host Company Department Assigned to

RT Lawrence Quality Assurance (IDA-RED)


Schedule (Date): Tuesday -Saturday (6:00am - 3:00pm) Number of Working Hours:
40

Getting Data Set / Table Type and Smart Assist Type (Week6)

By obtaining the dataset and identifying the table type, we determine how many tables a specific sentence from a test
script has utilized. We ascertain whether it's using multiple tables or just a single one. In our Smart Assist type, we
analyze whether the sentence of a test script is a drilldown, lateral, or zigzag. This analysis aids in understanding the
data retrieval patterns and query structures. It helps optimize the testing process and improve efficiency. Additionally,
it enhances our ability to identify potential issues and anomalies within the test scripts. Ultimately, this approach
contributes to the overall quality and effectiveness of our testing procedures.

Reviewed by: Date

OJT Supervisor Signature

Page 1 of 1
WEEKLY JOURNAL
Last Name First Name MI
Calising John Patrick B.

STI Campus Program Year Level Section


Balagtas BSIT 4th A

Host Company Department Assigned to

RT Lawrence Quality Assurance (IDA-RED)


Schedule (Date): Tuesday -Saturday (6:00am - 3:00pm) Number of Working Hours:
40

Checking Actual Result and Baseline (Week7)


By checking the actual result, we compare and identify the actual result and baseline to determine if there are no
changes, changes, or a bad run. We use IDA Regression and IDA View to check the actual result against the baseline. If
there's only a slight difference between the baseline and actual result, we need to know which one is more accurate. If
the actual result is more accurate, it will be set as the new baseline, forming our verdict. When checking the baseline,
we compare the SQL statements retrieved from IDA View, which can be seen in the debugging view. Additionally, the
SQL statements can also be viewed in DevTools for further verification.

Reviewed by: Date

OJT Supervisor Signature

Page 1 of 1
WEEKLY JOURNAL
Last Name First Name MI
Calising John Patrick B.

STI Campus Program Year Level Section


Balagtas BSIT 4th A

Host Company Department Assigned to

RT Lawrence Quality Assurance (IDA-RED)


Schedule (Date): Tuesday -Saturday (6:00am - 3:00pm) Number of Working Hours:
40

Quick Setup (Adding new synonym in smart assistant) (Week8)


Adding new synonyms in Smart Assistant involves incorporating given words into the system. Firstly, we must check
whether these words already exist within the Smart Assistant's root command. If any word is not present, we proceed
to save it for future reference. Conversely, if a word is already included, we cancel the addition to prevent redundancy.
Additionally, if the root command in Smart Assistant comprises multiple fields, we meticulously ensure that each field
is adequately filled with the relevant synonyms. This meticulous process guarantees the effectiveness and accuracy of
the Smart Assistant's language processing capabilities. Furthermore, it streamlines user interactions and enhances
overall usability. Regularly updating and expanding the synonym database enables the Smart Assistant to better
understand and respond to user queries across various domains.

Reviewed by: Date

OJT Supervisor Signature

Page 1 of 1

You might also like