ff-automationv2 2.2.32 → 2.2.33

package/dist/ai/llmprompts/llmPromptTypes/systemPromptTypes.d.ts

@@ -38,3 +38,6 @@ export type combinedActionArgs = {
 export type inputContextArgs = {
     inputStepsContext: any[];
 };
+export type arithmeticArgs = {
+    inputStepsContext: any[];
+};

package/dist/ai/llmprompts/promptRegistry.js

@@ -20,6 +20,7 @@ const inputContextPrompt_js_1 = require("./systemPrompts/inputContextPrompt.js")
 // import { combinedActionExtractorPrompt } from "./systemPrompts/combinedActionExtractorPrompt.js";
 const otpExtractorPrompt_js_1 = require("./systemPrompts/otpExtractorPrompt.js");
 const fileVerifyActionExtractorPrompt_js_1 = require("./systemPrompts/fileVerifyActionExtractorPrompt.js");
+const arithmeticPrompt_js_1 = require("./systemPrompts/arithmeticPrompt.js");
 exports.prompts = {
     web: {
         userStoryToList: userStoryToListPrompt_js_1.buildStepExtractionPrompt,
@@ -34,6 +35,7 @@ exports.prompts = {
         inputContextPrompt: inputContextPrompt_js_1.inputContextPrompt,
         otpExtractorPrompt: otpExtractorPrompt_js_1.otpExtractorPrompt,
         fileVerifyActionExtractorPrompt: fileVerifyActionExtractorPrompt_js_1.fileVerifyActionExtractorPrompt,
+        arithmeticPrompt: arithmeticPrompt_js_1.arithmeticPrompt,
     },
     android: {
         userStoryToList: userStoryToListPrompt_js_1.androidbuildStepExtractionPrompt,
@@ -48,6 +50,7 @@ exports.prompts = {
         inputContextPrompt: inputContextPrompt_js_1.inputContextPrompt,
         otpExtractorPrompt: otpExtractorPrompt_js_1.otpExtractorPrompt,
         fileVerifyActionExtractorPrompt: fileVerifyActionExtractorPrompt_js_1.fileVerifyActionExtractorPrompt,
+        arithmeticPrompt: arithmeticPrompt_js_1.arithmeticPrompt,
     },
     ios: {
         userStoryToList: userStoryToListPrompt_js_1.androidbuildStepExtractionPrompt,
@@ -62,5 +65,6 @@ exports.prompts = {
         inputContextPrompt: inputContextPrompt_js_1.inputContextPrompt,
         otpExtractorPrompt: otpExtractorPrompt_js_1.otpExtractorPrompt,
         fileVerifyActionExtractorPrompt: fileVerifyActionExtractorPrompt_js_1.fileVerifyActionExtractorPrompt,
+        arithmeticPrompt: arithmeticPrompt_js_1.arithmeticPrompt,
     }
 };

package/dist/ai/llmprompts/systemPrompts/actionExtractorPrompt.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.keywordExtractor = keywordExtractor;
 async function keywordExtractor({ priorAndNextSteps }) {
-    const allowedActions = ["enter", "refresh", "wait", "verify", "scroll", "navigate", "navigateBack", "click", "maximize", "minimize", "get", "upload", "close", "open", "drag_and_drop", "switch", "cleartext", "notwebopenaction", "mouseAction", "switchToAndroid", "getOtp"];
+    const allowedActions = ["enter", "refresh", "wait", "verify", "scroll", "navigate", "navigateBack", "click", "maximize", "minimize", "get", "upload", "close", "open", "drag_and_drop", "switch", "cleartext", "notwebopenaction", "mouseAction", "switchToAndroid", "getOtp", "arithmetic"];
     const prompt = `
 You are an expert in Web application testing.
     From the step, extract ONLY the meaningful keywords so that i can search for the element in the dom.
@@ -20,7 +20,10 @@ You are an expert in Web application testing.
   No type word in the step → only [name] as the keyword.
     Example: "click X filter dropdown" → ["X", "X filter", "X filter dropdown"]
   If more than 3 type words are attached to the element (chain would exceed 5 keywords), keep the core name plus only the 2-3 type words CLOSEST to the element name and drop the rest, so total keywords stay within the 3-5 max.
-    - When a step contains two elements connected by a positional or relational phrase, keywords MUST contain at least one keyword from each element — TARGET element first, then the reference element. Never omit the reference element. Example: "Click on x above y" → x is the target, y is the reference → ["x", "y"].
+    - When a step contains two elements connected by a positional or relational phrase, keywords MUST contain at least one keyword from each element — TARGET element first, then the reference element. Never omit the reference element. This includes positional connectors (above, below, next to, under, near) AND possessive/associative connectors (of, for) that link an attribute/property element to a named reference element. Do NOT merge the two elements into a single combined keyword string.
+    Example: "Click on x above y" → x is the target, y is the reference → ["x", "y"].
+    Example: "get Price of Learn Selenium" → Price is the target attribute, "Learn Selenium" is the reference element → keywords ["Price", "Learn Selenium"], elementName "Price".
+    Example: "verify Rating for Learn Selenium is 300" → ["Rating", "Learn Selenium"], elementName "Rating".
     - 3 to 5 keywords maximum. dont give more then 5 keywords. and no need for case sensitive.
     - General ordering rule: whenever a step involves both a target element and a reference/context element, the TARGET element's keyword(s) must always come FIRST, followed by the reference/context element's keyword(s). This applies to positional/relational steps, selection steps, and any other multi-element step.
     - For the open action if they are not provided anything like profile, capablities in the step in that case don't add them check whether the profile and the capablities are present in the step if not please don't add them.
@@ -49,7 +52,7 @@ You are an expert in Web application testing.
     - If the step is about entering text or Uploading file, Should NOT include input value from the step into keywords.
     - If the step has words like tag name audio, video, image,svg, checkbox etc, include them in the keywords.
     - **If icon is mentioned in step then 'svg' should add in keywords ex: click on x icon -> [x, x icon,svg] and for Upload action first keyword should be 'file'. ex: upload file in x  -> [file,x].**
-    - Do NOT split single-word keywords and do NOT include relation terms (above, below, next to, etc.) in keywords.
+    - Do NOT split single-word keywords and do NOT include relation terms (above, below, next to, of, for, etc.) in keywords.
     - Treat each keyword independently never merge different keywords.
     - Keywords can be string or number if the step contains a number as part of the ELEMENT's name/label (e.g. "click on Step 2 tab" -> "Step 2" is a keyword). This does NOT apply to numbers that are the value being entered/typed/uploaded — those stay excluded per the "entering text or Uploading file" rule below, even if numeric (e.g. "Enter 5 in Quantity field" -> "5" is NOT a keyword).
     - Do Not include any other unrelated keywords for step. 
@@ -58,7 +61,7 @@ You are an expert in Web application testing.
     - If the step is for the switching to android then provide the action as the switchToAndroid
     - element_name: extract name of the element that mentioned in the the step.(eg:tap on x -> element_name:x) keep element_name as short as possible and make the first letter of first word of the element_name as capital. because element_name is also used to find element in the dom. and if element_name is not mentioned in step then return action of the step as element_name.
     - Set action to notwebopenaction only when the instruction is related to a mobile application, app, application, installed package, or bundle .
-    - action: click for taping, clicking or selecting, enter for entering input, wait for waiting or sleeping,scroll for scrolling and swiping, navigate for navigating to page using url, navigateBack for navigateing back to previous page, get for getting,fetching element,maximize for maximizing browser window, close for closing browser window,open for opening browser window, upload for uploading file using path, drag_and_drop for dragging and dropping element, switch is for switching to tab or window or frame,cleartext for clearing or removing text from element, mouseAction for the action related mouse actions even for mouse click , refresh is for refreshing or reloading pages, getOtp for fetching/reading an OTP value.
+    - action: click for taping, clicking or selecting, enter for entering input, wait for waiting or sleeping,scroll for scrolling and swiping, navigate for navigating to page using url, navigateBack for navigateing back to previous page, get for getting,fetching,capturing,reading element or text,maximize for maximizing browser window, close for closing browser window,open for opening browser window, upload for uploading file using path, drag_and_drop for dragging and dropping element, switch is for switching to tab or window or frame,cleartext for clearing or removing text from element, mouseAction for the action related mouse actions even for mouse click , refresh is for refreshing or reloading pages, getOtp for fetching/reading an OTP value, arithmetic for performing arithmetic operations (multiply, divide, add, subtract, calculate).
     - If mouse action related step is there select mouseAction from the allowed actions list check for the step and provide it.
     - action must be one of from this list  ${JSON.stringify(allowedActions)}.if not one of them, return '0'. if step about set or find action return '0'
     - For navigate action, keywords should contain only one keyword which is full url from the step and should not include any other text. and if step has another actions, including navigate action, don't return navigate action return another action which is in the step. and element_name should be "URL".
@@ -92,7 +95,7 @@ You are an expert in Web application testing.
           "keywords": ["key1", "key2"],
           "elementName": "element name",
           "action": ${allowedActions.join("|")},
-          "isStepValueDependable": boolean (true ONLY if action is verify/enter AND the step contains an actual referential phrase pointing to an earlier step's data — see isStepValueDependable rule below for the full test and examples; false if the value is literal or no referential phrase is present. Never consider future steps.),
+          "isStepValueDependable": boolean,
           "liveLog": "Should Generate a short, human-readable description of what the AI is about to do.",
           "fileType": "pdf" | other lowercase file extension | null,
           "step": Return the original step exactly as-is if it contains a single action; if multiple actions exist, split into atomic steps without changing any wording, spelling, casing, spacing, or punctuation.(Rules: No rephrasing, no additions/removals—each output step must be an exact substring of the input.)
@@ -104,13 +107,14 @@ You are an expert in Web application testing.
     STEP RULES (VERY IMPORTANT):
 
     - Each "step" MUST represent EXACTLY ONE action.
-    - isStepValueDependable (boolean):
-      • Test is REFERENTIAL vs LITERAL, not sentence completeness — e.g. "enter 2nd step input in name" is a complete sentence but still referential, since the value itself isn't written there.
-      • Set true ONLY when action is 'verify' or 'enter' AND the step contains an actual referential phrase pointing to data from an earlier step (by step number, "previous/prior/earlier/that/same" wording, or naming what was fetched/copied/retrieved there). Confirm the referenced step exists earlier in priorAndNextSteps, never a future step.
-      • Set false when the value is written literally, or no referential phrase is present, or the action isn't verify/enter.
-      • DO NOT infer true from an element/field name alone when that word appears only in the CURRENT step's own target/element — e.g. "get text from Password" is false because "Password" there is just this step's own target, not a value pointing elsewhere.
-      • EXCEPTION — reference-by-element-name: if the VALUE being entered matches (case-insensitively) the elementName or keyword of a 'get' or 'enter' action from an EARLIER step in priorAndNextSteps, treat this as referential (true) even with no explicit pointer wording like "previous"/"same" — this is a common shorthand for "reuse whatever was entered/fetched there". Example: step 2 is "enter santosh@123 in password" (elementName "Password"), step 3 is "enter password in confirm password" → true, because the value "password" matches step 2's elementName, meaning step 3 is reusing step 2's entered value, not typing the literal word "password".
-      • Examples (illustrative, not exhaustive): "enter 2nd step input in name" → true. "enter the OTP received earlier in name" → true. "enter 'John' in name" → false. "get text from Password" → false (no reference present). "enter password in confirm password" (given step 2 entered a value into a "Password" field) → true.
+** isStepValueDependable (boolean):
+  • Set true when action is 'verify' or 'enter' and the step contains a value, comparison value, or referenced subject that represents data from another step, calculated result, or a referenced element/variable. Any explicit or implicit reference to existing, extracted, fetched, retrieved, copied, entered, calculated, or relationally referenced data must be treated as dependable (e.g., "enter calculated final result", "verify calculated value", "enter atpValue in field"). Resolve the reference using priorAndNextSteps when applicable; never consider future steps.
+  • Set true when action is 'arithmetic' and the step depends on values or variables from earlier steps (e.g., "Multiply atpValue by 3", "Subtract atpdivValue from atpValue", "Store captured value in variable atpValue").
+  • Set false only when the action has no reference to existing or earlier step data.
+  • Example: "verify extracted x text is x" → true when "extracted x text" refers to previously obtained data.
+  • Example: "enter that value in x" → true when "that value" refers to previously obtained data.
+  • Example: "Multiply atpValue by 3" → true when "atpValue" refers to a value captured in an earlier step.
+
     - Step MUST be rewritten as a CLEAN and COMPLETE instruction.
     - Step MUST contain:
       • action

package/dist/ai/llmprompts/systemPrompts/arithmeticPrompt.d.ts

@@ -0,0 +1,2 @@
+import { arithmeticArgs } from "../llmPromptTypes/systemPromptTypes.js";
+export declare function arithmeticPrompt({ inputStepsContext, }: arithmeticArgs): Promise<string>;

package/dist/ai/llmprompts/systemPrompts/arithmeticPrompt.js

@@ -0,0 +1,48 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.arithmeticPrompt = arithmeticPrompt;
+async function arithmeticPrompt({ inputStepsContext, }) {
+    const arithmetic = ["multiply", "divide", "add", "subtract"];
+    const prompt = `
+You are an intelligent assistant that extracts arithmetic operations and operands from test steps.
+
+Previous steps data:
+${JSON.stringify(inputStepsContext, null, 2)}
+
+Instructions:
+1. Analyze the current step and use Previous steps data to resolve any operand that refers to data from an earlier step.
+2. Extract exactly two operands, their corresponding variable names when available, the arithmetic operation, and the target variable name.
+
+Rules for "operation":
+  - Return ONLY one of: "multiply", "divide", "add", "subtract".
+- Determine the operation directly from the current step.
+
+Rules for "operandOne" and "operandTwo":
+  - If an operand is a literal number, return only the numeric value as a string.Remove currency symbols, special characters, commas, or other non - numeric symbols.Example: "$2" -> "2".
+- If an operand refers to an earlier step or its value using contextual or relational wording, find the matching step in Previous steps data and use that step's inputText/value as the operand and its variableName as the corresponding operandVariableName.
+  - If the referenced earlier step contains both inputText and variableName, always use the inputText for the operand and the exact variableName for its operandVariableName.
+- If an operand is a variable already present in Previous steps data, use its exact variableName.
+- If no variableName exists for a literal operand, set its operandVariableName to null.
+- Do not include symbols, descriptions, element names, or explanations in operandOne or operandTwo.
+
+Rules for "subtract":
+  - "Subtract X from Y" -> operandOne = Y, operandTwo = X.
+- For other subtraction wording, follow the operand order expressed by the step.
+
+Rules for "variableName":
+  - If the current step explicitly provides a target variable name, use that exact name without modifying it.
+- Otherwise, generate a valid descriptive variable name based on the operation and result.
+- The generated name must contain only letters, digits, or underscores and must not start with a digit.
+
+Respond ONLY with valid JSON in this exact format:
+{
+  "operandOne": "x",
+  "operandTwo": "y",
+  "operandOneVariableName": "variableName1 | null",
+  "operandTwoVariableName": "variableName2 | null",
+  "operation": ${arithmetic.join("|")},
+  "variableName": "targetVariableName"
+}
+`;
+    return prompt;
+}

package/dist/ai/llmprompts/systemPrompts/getActionExtractorPrompt.js

@@ -32,7 +32,7 @@ Select the perfect matching NLP name from the list that best fits the step's int
 }
 Rules:
 - nlpName must be exactly one from the provided list.
-- "variableName": Generate a valid, descriptive variable name for storing the fetched value based on the step intent (e.g., valid camelCase identifier such as "pageTitle", "extractedText", "userEmail", "itemPrice", "orderId"). It must be a valid programming identifier (letters, numbers, underscores; cannot start with a number; no spaces or special characters).
+"variableName": Generate a valid, descriptive variable name for storing the fetched value based on the step intent (e.g., a valid camelCase identifier such as "pageTitle", "extractedText", "userEmail", "itemPrice", or "orderId"). It must be a valid programming identifier (letters, numbers, and underscores; cannot start with a number; no spaces or special characters). If a variable name is explicitly mentioned in the step, use it exactly as provided. Otherwise, generate a variable name based on the step intent and always try to maintain a similar length to the variable name mentioned in the step.
 - Use context from the steps : ${priorAndNextSteps}, keyword and json to search for FF-inspecter.
 - **Find the FF-inspecter attribute value of the element in the Simplified DOM  whose text or attributes best match the step.**
 - **CRITICAL: For media actions (GetVideo..., GetAudio...), ALWAYS prioritize the actual <video> or <audio> element. DO NOT select container <div>, <span> or code block elements that merely contain the media tag as text. If you see a code block and a real media element, choose the real media element.**

package/dist/ai/llmprompts/systemPrompts/getActionExtractorPromptMob.js

@@ -30,7 +30,7 @@ Return **only valid JSON** in the following format:
 }
 Rules:
 - nlpName must be exactly one from the provided list.
-- "variableName": Generate a valid, descriptive variable name for storing the fetched value based on the step intent (e.g., valid camelCase identifier such as "deviceDate", "extractedText", "batteryLevel", "currentOrientation"). It must be a valid programming identifier (letters, numbers, underscores; cannot start with a number; no spaces or special characters).
+"variableName": Generate a valid, descriptive variable name for storing the fetched value based on the step intent (e.g., a valid camelCase identifier such as "pageTitle", "extractedText", "userEmail", "itemPrice", or "orderId"). It must be a valid programming identifier (letters, numbers, and underscores; cannot start with a number; no spaces or special characters). If a variable name is explicitly mentioned in the step, use it exactly as provided. Otherwise, generate a variable name based on the step intent and always try to maintain a similar length to the variable name mentioned in the step.
 - for screenshots, extract the inputText from the step. like what they what to name image.if not present then leave it empty.
 - Use context from the steps : ${priorAndNextSteps}, json to search for FF-inspecter.
 - **Find the FF-inspecter attribute value of the element in the Simplified JSON whose text or attributes best match the step.**

package/dist/ai/llmprompts/systemPrompts/inputContextPrompt.js

@@ -13,6 +13,8 @@ Instructions:
 1. Analyze the current step and previous steps carefully.
 
 2. Priority rules (strict order):
+   - If a specific variable name is mentioned (e.g., "atpValue", "atpMulValue", "atpdivValue", "finalResult") → match to the step in "Previous steps data" with that exact "variableName".
+   - If referential calculation phrases are mentioned (e.g., "calculated final result", "calculated value", "final result", "calculation result", "result of calculation") → match to the most recent calculation or arithmetic step in "Previous steps data".
    - If a step index or step reference is mentioned (e.g., "step 2", "2nd step", "3rd step", "3nd step", "step 1.1", "sub-step 1.1") → match to the corresponding stepindex (e.g., 2nd step -> stepindex 2, step 1.1 -> sub-step with stepindex "1.1"). If the matched step contains "subSteps", extract from the subStep matching the field name or sub-step index, and extract ONLY from that subStep.
    - If a field name is mentioned (e.g., email, password, first name) → extract from the matching field step or subStep.
    - If words like "above", "previous", "same" → extract from the most relevant previous step or subStep.

package/dist/ai/llmprompts/systemPrompts/mobileKeywordExtractor.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.keywordExtractorMobile = keywordExtractorMobile;
 async function keywordExtractorMobile({ priorAndNextSteps }) {
-    const allowedActions = ["openApp", "tap", "enter", "wait", "verify", "scroll", "get", "closeApp", "combined", "switchToWeb", "getOtp", "enterOtp"];
+    const allowedActions = ["openApp", "tap", "enter", "wait", "verify", "scroll", "get", "closeApp", "combined", "switchToWeb", "getOtp", "enterOtp", "arithmetic"];
     const prompt = `
 You are an expert in mobile app testing.
 From the step, extract ONLY the meaningful keywords so that i can search for the element in the dom.
@@ -30,7 +30,7 @@ Rules:
 - If the step is for the switching to web then provide the action as the switchToWeb
 - If an element label contains multiple words (e.g., "Sign In", "Add to Cart"), keep them together as ONE keyword and do not split them and also for keywords you generated, do not split them.
 -** element_name: extract name of the element that mentioned in the step  not from keywords or other steps.(eg:tap on x -> element_name:x). always try to retuen short and meaning full element name from step**
-- action: openApp for opening or launching of app  and activate app is there in step give action as combined, tap for taping or selecting or clicking or pressing, enter for entering input, wait for waiting or sleeping, verify for verifying or checking,scroll for scrolling and swiping, get for getting and fetching element and gtting logs and getting driver or instance details, closeApp for closing the app but not for terminating app step.
+- action: openApp for opening or launching of app  and activate app is there in step give action as combined, tap for taping or selecting or clicking or pressing, enter for entering input, wait for waiting or sleeping, verify for verifying or checking,scroll for scrolling and swiping, get for getting and fetching element and gtting logs and getting driver or instance details, closeApp for closing the app but not for terminating app step, arithmetic for performing arithmetic operations (multiply, divide, add, subtract, calculate) or storing/assigning calculation results and captured values into variables.
 - If step is press any key give action as tap.if step is clear or clearandenter give action as enter and if step is open chrome browser app por application and it doesnot have app package or bundle id give action as combined but if step has app package or bundle id give action as openApp.
 - action must be one of from this list ${allowedActions}.if not one of them, return action as 'combined'. if step about set or setting or find, install apk or ipa, uninstall apk or ipa,activate app with app package or bundle id, pinch in or pinch out or related turn wifi or airplane mode return action as 'combined'
 - if the step action is about finding or check app is installed or open chrome browser  or open notification bar or terminate app using app package or bumdle id or running app in the background for some seconds then provide action as combined.

package/dist/ai/llmprompts/userPrompts/userPrompt.js

@@ -15,6 +15,7 @@ exports.userInputFormatters = {
     [promptType_js_1.PromptType.INPUT_CONTEXT_PROMPT]: (userInput) => `Extract the input text from the following context:\n\n${JSON.stringify(userInput.currentStep, null, 2)}`,
     [promptType_js_1.PromptType.OTP_EXTRACTOR]: (userInput) => `Extract the OTP from this SMS body:\n\n${JSON.stringify(userInput.smsBody, null, 2)}`,
     [promptType_js_1.PromptType.FILE_VERIFY_PROMPT]: (userInput) => `Extract the file verification action data for the following step:\n\n${JSON.stringify(userInput.currentStep, null, 2)}`,
+    [promptType_js_1.PromptType.ARITHMETIC_PROMPT]: (userInput) => `Extract arithmetic operation details for the following step:\n\n${JSON.stringify(userInput.currentStep, null, 2)}`,
     [promptType_js_1.PromptType.VISION_PROMPT]: (userInput) => {
         let imageBase64 = null;
         if (userInput.annotatedScreenshot) {

package/dist/automation/actions/executor.d.ts

@@ -378,4 +378,5 @@ export declare class ActionExecutor implements IActionExecutor {
         regex: string;
     } | null>, returnTypeVariableName?: string): Promise<void>;
     verifyPDF(value: string, isDownload?: boolean, filePath?: string | null): Promise<void>;
+    arithmetic(result: any): Promise<void>;
 }

package/dist/automation/actions/executor.js

@@ -359,6 +359,7 @@ const mouseReleaseLeftMouseButton_js_1 = require("./interaction/mouse/mouseRelea
 const mouseClickOnCurrentCursorNTImes_js_1 = require("./interaction/mouse/mouseClickOnCurrentCursorNTImes.js");
 const getOtp_js_1 = require("./interaction/elementlessActions/getOtp.js");
 const VerifyPDF_js_1 = require("./interaction/files/VerifyPDF.js");
+const arithmeticOperations_js_1 = require("./interaction/arithmetic/arithmeticOperations.js");
 class ActionExecutor {
     constructor(driver, scriptDataAppender, elementGetter, platform, adbPath, stepsInputData) {
         this.driver = driver;
@@ -6708,5 +6709,29 @@ class ActionExecutor {
             throw error;
         }
     }
+    async arithmetic(result) {
+        try {
+            await (0, arithmeticOperations_js_1.performArithmeticOperation)({
+                operandOne: result.operandOne,
+                operandTwo: result.operandTwo,
+                operandOneVariableName: result.operandOneVariableName,
+                operandTwoVariableName: result.operandTwoVariableName,
+                operation: result.operation,
+                variableName: result.variableName,
+                returnTypeVariableName: result.returnTypeVariableName || result.variableName || this.currentReturnTypeVariableName || this.currentVariableName,
+                stepIndex: result.stepIndex ?? this.currentStepIndex,
+                currentStep: result.currentStep ?? this.currentStepText,
+                manualStep: result.manualStep ?? this.manualStepText,
+                stepsInputData: result.stepsInputData ?? this.stepsInputData,
+                scriptDataAppender: this.scriptDataAppender,
+                platform: this.platform,
+                elementGetter: this.elementGetter,
+            });
+        }
+        catch (error) {
+            logData_js_1.logger.error("Error in [ActionExecutor] arithmetic", error);
+            throw error;
+        }
+    }
 }
 exports.ActionExecutor = ActionExecutor;

package/dist/automation/actions/interaction/alert/enterDataToAlert.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.enterDataToAlert = enterDataToAlert;
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function enterDataToAlert(args) {
     try {
         await args.driver.sendAlertText(args.value);
@@ -11,7 +11,7 @@ async function enterDataToAlert(args) {
             nlpName: "EnterDataToAlert",
             stepInputs: [args.variableName ? `variable:${args.variableName}` : args.value],
         });
-        (0, getHelper_js_1.saveStepInputData)(args, args.value);
+        (0, saveStepInputData_js_1.saveStepInputData)(args, args.value);
     }
     catch (error) {
         args.scriptDataAppender.setErrorNLP("EnterDataToAlert");

package/dist/automation/actions/interaction/alert/getTextPresentOnAlertPopup.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.getTextPresentOnAlertPopup = getTextPresentOnAlertPopup;
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function getTextPresentOnAlertPopup(args) {
     try {
         const text = await args.driver.getAlertText();
@@ -11,7 +11,7 @@ async function getTextPresentOnAlertPopup(args) {
             nlpName: "GetTextPresentOnAlertPopup",
             returnTypeVariableName: args.returnTypeVariableName
         });
-        (0, getHelper_js_1.saveStepInputData)(args, text);
+        (0, saveStepInputData_js_1.saveStepInputData)(args, text);
     }
     catch (error) {
         args.scriptDataAppender.setErrorNLP("GetTextPresentOnAlertPopup");

package/dist/automation/actions/interaction/arithmetic/arithmeticOperations.d.ts

@@ -0,0 +1,2 @@
+import { ArithmeticActionInterface } from "../../interface/arithmeticActionInterface.js";
+export declare function performArithmeticOperation(args: ArithmeticActionInterface): Promise<void>;

package/dist/automation/actions/interaction/arithmetic/arithmeticOperations.js

@@ -0,0 +1,61 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.performArithmeticOperation = performArithmeticOperation;
+const logData_js_1 = require("../../../../utils/logger/logData.js");
+const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
+async function performArithmeticOperation(args) {
+    try {
+        const normalizedOp = (args.operation || "").toLowerCase().trim();
+        const num1 = parseFloat(args.operandOne);
+        const num2 = parseFloat(args.operandTwo || "0");
+        let result;
+        let operation = "";
+        switch (normalizedOp) {
+            case "add":
+                result = num1 + num2;
+                operation = "+";
+                break;
+            case "subtract":
+                result = num1 - num2;
+                operation = "-";
+                break;
+            case "multiply":
+                result = num1 * num2;
+                operation = "*";
+                break;
+            case "divide":
+                if (num2 === 0) {
+                    throw new Error("Division by zero in arithmetic operation.");
+                }
+                result = num1 / num2;
+                operation = "/";
+                break;
+            default:
+                throw new Error(`Unsupported arithmetic operation: '${args.operation}'. Supported operations are addition, subtraction, multiplication, division.`);
+        }
+        const calculatedResult = (result).toString();
+        args.returnTypeVariableName = args.returnTypeVariableName || args.variableName;
+        if (args.scriptDataAppender) {
+            const stepInputs = [
+                args.operandOneVariableName ? `variable:${args.operandOneVariableName}` : String(num1),
+                operation,
+                args.operandTwoVariableName ? `variable:${args.operandTwoVariableName}` : String(num2),
+            ];
+            (0, appendScriptData_js_1.appendScriptData)({
+                scriptDataAppender: args.scriptDataAppender,
+                nlpName: "ArithmeticOperationsOnOperands",
+                stepInputs,
+                elementGetter: args.elementGetter,
+                platform: args.platform,
+                returnTypeVariableName: args.returnTypeVariableName,
+            });
+        }
+        (0, saveStepInputData_js_1.saveStepInputData)(args, calculatedResult);
+        logData_js_1.logger.info(`Arithmetic operation performed: ${num1} ${operation} ${num2} = ${result}`);
+    }
+    catch (error) {
+        args.scriptDataAppender?.setErrorNLP("ArithmeticOperationsOnOperands");
+        throw new Error(`Arithmetic action failed`, { cause: error });
+    }
+}

package/dist/automation/actions/interaction/clear/clearAndEnter.js

@@ -3,7 +3,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.clearAndEnter = clearAndEnter;
 const enterActionHelper_js_1 = require("../../../../utils/helpers/enterActionHelper.js");
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function clearAndEnter(args) {
     const nlpName = args.platform === "ios" ? "IOS_ClearThenEnterInput" : "MOB_ClearThenEnterInput";
     switch (args.platform) {
@@ -27,7 +27,7 @@ async function clearAndEnter(args) {
                     selector: args.selector,
                     platform: args.platform
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP(nlpName);
@@ -54,7 +54,7 @@ async function clearAndEnter(args) {
                     selector: xpathPath,
                     platform: args.platform
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP("ClearThenEnterInput");

package/dist/automation/actions/interaction/elementlessActions/getOtp.js

@@ -4,7 +4,7 @@ exports.GetOtpAction = GetOtpAction;
 const logData_js_1 = require("../../../../utils/logger/logData.js");
 const child_process_1 = require("child_process");
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function GetOtpAction(args) {
     try {
         // const udid = (args.driver.capabilities as any)["appium:udid"] || (args.driver.capabilities as any).udid;
@@ -30,12 +30,12 @@ async function GetOtpAction(args) {
         if (existingSms && now - existingSms.date <= (timeFrom * 1000)) {
             const smsBody = existingSms.body;
             logData_js_1.logger.info("SMS body:", smsBody);
-            let regex;
+            let _regex;
             let otpValue;
             if (args.otpExtractor) {
                 const otpResult = await args.otpExtractor(smsBody);
                 if (otpResult?.otp && otpResult.regex) {
-                    regex = otpResult.regex;
+                    _regex = otpResult.regex;
                     otpValue = otpResult.otp;
                     logData_js_1.logger.info("Extracted OTP:", otpResult.otp, "Generated Regex:", otpResult.regex);
                 }
@@ -50,7 +50,7 @@ async function GetOtpAction(args) {
                 platform: "android",
                 returnTypeVariableName: args.returnTypeVariableName
             });
-            (0, getHelper_js_1.saveStepInputData)(args, otpValue || smsBody);
+            (0, saveStepInputData_js_1.saveStepInputData)(args, otpValue || smsBody);
             return;
         }
         const baselineId = existingSms?.id;
@@ -88,7 +88,7 @@ async function GetOtpAction(args) {
                     platform: "android",
                     returnTypeVariableName: args.returnTypeVariableName
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, otpValue || smsBody);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, otpValue || smsBody);
                 return;
             }
             await new Promise((resolve) => setTimeout(resolve, 2000));

package/dist/automation/actions/interaction/enterActions/EnterInputIntoElementFromClipBoardInterface_mob.js

@@ -4,7 +4,7 @@ exports.MOB_EnterInputIntoElementFromClipBoard = MOB_EnterInputIntoElementFromCl
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
 const enterActionHelper_js_1 = require("../../../../utils/helpers/enterActionHelper.js");
 const logData_js_1 = require("../../../../utils/logger/logData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function MOB_EnterInputIntoElementFromClipBoard(args) {
     try {
         const { ffNumber, xpathPath } = (0, enterActionHelper_js_1.enterActionHelperMob)(args.pageDOM, args.fireflinkIndex);
@@ -26,7 +26,7 @@ async function MOB_EnterInputIntoElementFromClipBoard(args) {
             selector: args.selector,
             platform: args.platform
         });
-        (0, getHelper_js_1.saveStepInputData)(args, value);
+        (0, saveStepInputData_js_1.saveStepInputData)(args, value);
     }
     catch (error) {
         args.scriptDataAppender.setErrorNLP("MOB_EnterInputIntoElementFromClipBoard");

package/dist/automation/actions/interaction/enterActions/enterInput.js

@@ -37,7 +37,7 @@ exports.enterInput = enterInput;
 const enterActionHelper_js_1 = require("../../../../utils/helpers/enterActionHelper.js");
 const logData_js_1 = require("../../../../utils/logger/logData.js");
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function enterInput(args) {
     const nlpName = args.platform === "ios" ? "IOS_SendKeys" : "MOB_SendKeys";
     switch (args.platform) {
@@ -79,7 +79,7 @@ async function enterInput(args) {
                     selector: args.selector,
                     platform: args.platform
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP(nlpName);
@@ -111,7 +111,7 @@ async function enterInput(args) {
                     selector: xpathPath,
                     platform: args.platform
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP("SendKeys");

package/dist/automation/actions/interaction/enterActions/enterInputAndPress.js

@@ -3,7 +3,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.enterInputAndPress = enterInputAndPress;
 const enterActionHelper_js_1 = require("../../../../utils/helpers/enterActionHelper.js");
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function enterInputAndPress(args) {
     switch (args.platform) {
         case "android":
@@ -54,7 +54,7 @@ async function enterInputAndPress(args) {
                     selector: args.selector,
                     platform: args.platform
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, inputValue || args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, inputValue || args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP("MOB_EnterDataAndPressKey");
@@ -109,7 +109,7 @@ async function enterInputAndPress(args) {
                     selector: xpathPath,
                     platform: args.platform
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, inputValue || args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, inputValue || args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP("EnterDataAndPressKey");

package/dist/automation/actions/interaction/enterActions/enterUrl.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.enterUrl = enterUrl;
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function enterUrl(args) {
     const nlpName = args.platform === "ios" ? "IOS_EnterUrl" : "MOB_EnterUrl";
     switch (args.platform) {
@@ -24,7 +24,7 @@ async function enterUrl(args) {
                     nlpName: nlpName,
                     stepInputs: [args.variableName ? `variable:${args.variableName}` : args.value],
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP(nlpName);
@@ -40,7 +40,7 @@ async function enterUrl(args) {
                     nlpName: 'EnterURL',
                     stepInputs: [args.variableName ? `variable:${args.variableName}` : args.value],
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP("EnterURL");

package/dist/automation/actions/interaction/enterActions/enterusingJs.js

@@ -4,7 +4,7 @@ exports.enterInputUsingJs = enterInputUsingJs;
 const enterActionHelper_js_1 = require("../../../../utils/helpers/enterActionHelper.js");
 const logData_js_1 = require("../../../../utils/logger/logData.js");
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function enterInputUsingJs(args) {
     try {
         const { ffNumber, xpathPath } = (0, enterActionHelper_js_1.enterActionHelper)(args.pageDOM, args.fireflinkIndex);
@@ -30,7 +30,7 @@ async function enterInputUsingJs(args) {
             selector: xpathPath,
             platform: args.platform
         });
-        (0, getHelper_js_1.saveStepInputData)(args, args.value);
+        (0, saveStepInputData_js_1.saveStepInputData)(args, args.value);
     }
     catch (error) {
         args.scriptDataAppender.setErrorNLP("EnterInputUsingJS");

package/dist/automation/actions/interaction/enterActions/waitAndEnter.js

@@ -3,7 +3,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.waitAndEnter = waitAndEnter;
 const enterActionHelper_js_1 = require("../../../../utils/helpers/enterActionHelper.js");
 const appendScriptData_js_1 = require("../../../../fireflinkData/fireflinkScript/appendScriptData.js");
-const getHelper_js_1 = require("../../../../utils/helpers/getHelper.js");
+const saveStepInputData_js_1 = require("../../../../utils/helpers/saveStepInputData.js");
 async function waitAndEnter(args) {
     const DEFAULT_WAIT = 5;
     const parseValue = (value) => {
@@ -38,7 +38,7 @@ async function waitAndEnter(args) {
                     selector: args.selector,
                     platform: args.platform
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, inputValue || args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, inputValue || args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP("MOB_WaitAndSendKeys");
@@ -74,7 +74,7 @@ async function waitAndEnter(args) {
                     selector: args.selector,
                     platform: args.platform
                 });
-                (0, getHelper_js_1.saveStepInputData)(args, inputValue || args.value);
+                (0, saveStepInputData_js_1.saveStepInputData)(args, inputValue || args.value);
             }
             catch (error) {
                 args.scriptDataAppender.setErrorNLP("WaitAndSendKeys");