DETAILED ACTION
This action is responsive to the Applicant’s response filed 11/24/25.
As indicated in Applicant’s response, claims 1, 8, 15 have been amended. Claims 1-20 are pending a next office action.
Claim Objections
Claims 15-20 are objected to because of the following informalities: the “non-tangible” characterization of the “computer-readable medium” (in the pre-amble) appears to be a typographical error as the exact phrasing for this characterization is shown as “tangible non-transitory” in the Specifications (para 0031). Appropriate correction is required lest a statutory rejection under USC § 101 be issued.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 1-5, 8-12, 15-19 is/are rejected under § 35 U.S.C. 103 as being unpatentable over Magre et al, USPubN: 2018/0137035 (herein Magre) in view of Kulkarni et al, USPubN: 2017/0220459 (herein Kulkamy), Marullo et al, USPN: 6,185,701 (herein Marullo) and Tammariello et al, USPubN: 2019/0065353 (herein Tammariello) further in view of Abu El Ata USPubN: 2012/0197686 (herein AbuAta) and Conti et al, USPubN: 2018/0067844 (herein Conti).
As per claim 1, Magre discloses a system of quality assurance and performance testing of supply chain applications and systems (series of - para 0011; simultaneously or in sequence - para 0010), comprising:
a computer comprising a processor, memory, and one or more testing components (e.g.
test functionalities of web application across different platforms - Abstract, para 0013; series of
coordinated activities ... test web applications - para 00ll; application testing tools – para 0015); and
a database(test data repository - para 0045), communicatively coupled with the computer, and comprising one or more testing application programming interfaces (e.g. test case repository ... for testing ... functionalities of the web application - para 0025; repository 112 may include workflows ... workflow may specify atomics or test cases - para 0027; web objects of web application 150 … information about ... web object repository 111 - para 0021; types of web objects and code of those web objects ... saved ... web object repository 111 - para 0022 – Note1: repository storing code for web objects and repository storing atomics and test cases for workflow reads on a database for storing testing submitted from other development applications) and
at least one properties file comprising a map (map of key value pairs ... in test data repository - para 0045) between a user interface element (key represents an identifier of an item ... unique identifiers for the login ID and password - para 0045) and its locator (actual login ID, name or email address, actual password of the user - para 0045), wherein the at least one properties file
wherein the at least one properties collection (configuration parameters 252,253 - Fig.
2B; test data spreadsheet file ... map of key pairs of the test data - para 0045) comprises identifying actual values for selector, value and dataset elements, wherein the selector, value and dataset elements are stored as key=value pairs (map of key value pairs 254- Fig. 2B; keys may be
unique identifiers ... values may be actual password of the user, key value pairs may be a JAVA map
-para 0045; first map of key-value pairs for test data from the test data repository; second map of
key-value pairs for test data from the ... repository - claim 1, pg. 8);
wherein the computer is configured to:
configure a test distribution to execute test case references in web application test case files
for a predefined number of concurrent users (on multiple platforms simultaneously - para 0010; test cases in parallel - para 0014; testing on the selected platforms ... in parallel - para 0018 - Note2: configuring multiple platforms for simultaneous testing respective web applications to consolidate test results into a test manager reads on test distribution by a manager according to a predefined platforms executing concurrently corresponding test cases, each hosted test application interacting with or accessed by a user - see: software testing ... user may access and interact with the web application through a web browser - para 0011);
provide a user interface (through a framework and user interface - para 0013) for receiving the web application test case files (test cases to test different functionalities of the application - para
0013),
wherein each web application test case file describes one or more actions (functionalities
of the application - para 0013; functionalities to be tested - para 0018; for testing login functionality - para 0031) to be tested and properties collections (test data 211 - para 0045) that each maps (map of key value pairs - para 0045) one or more elements to one or more values,
wherein each properties collection comprises a mapping between one or more web elements (map of key value pairs from above; keys may be ... login ID and password, values may be ... name or email address, actual password - para 0045) and corresponding locator types and values (map of key value pairs 254 - Fig. 2B; atomic ... finding a location of an element - para 0026; map of key value pairs, keys may be ... login ID and password, values may be ... name or email address, actual password - para 0045);
translate received web application test case files and corresponding properties collections (see above) into web application test cases (steps 251,252,254,255 - Fig. 2B; para 0044- 0047);
execute the web application test cases in parallel mode (test cases ... in parallel - para 0054) by identifying the one or more actions (functionalities to test - para 0055; interaction of a user with the web application - para 0039; testing login functionality - para 0031) identified in each web application test case (see above) and automatically invoking one or more testing components configured to execute a test using the one or more actions (interactions with the testing tool - para 0064; different actions on the social media application through different platforms - para 0039).
Magre does not explicitly disclose properties collection having a map as a properties file
Tammariello discloses distributed web-based test systems (Fig. IA) implemented with multi-threaded execution (para 0027) and configuration of test actions from use of a JSON file structure that also include key-value pairs structures or constructs (para 0076)
Thus, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement collection of test configuration and parametric setting in form of a properties file as shown in JSON format by Tammariello; because
file format can be stored, updated and managed in controllable environment and portable for use into across Internet-based environments, notably when the file structure in which information is stored is compliant with web/http transfer protocol and browser native application runtime, in that information capture adapted with JSON or XML like methodologies as set forth above in terms of structured correspondence between cells, value and associated object data would highly facilitate information mapping such as key-value pair collected in configuration test data by Magre, where proprieties file written in this format can be highly manageable, updatable and transportable for use across multiple web-based test configuration environments
Magre does not explicitly disclose test distribution to multiple platforms as
a configured test plan to execute test case references in web application test case files for a
predefined number of iterations
However, Magre discloses a test case for a login functionality in terms of test packagers that configure test cases with parameters, web objects and designating platforms to perform the test cases (Fig. 2A, 2B), the packaging scenario being repeated (method 250 may be repeated - para 0048) for
constructing the test cases on the same platforms; hence configuring a test packaging entails a planning a test scenario or distribution for a given test package that is iteratively deployed.
Implementation of automated execution of test case via a test case management platform is shown in Kulkarni, where plural thin-clients' virtual web browsers (Fig. 2-3) are configured to run chat test software as web-based CRM instances of 1/0 associated with call center, services accepting
customer communication (requests and responses) according to initiation of a test plan (para 0035),
with use of servers under the CRM platform allowing many iterations of each programmed test plan to be run concurrently (para 0008) by said virtual browsers, the test plan prescribing interactions between respective thin client agent, call center agent and system generated virtual customer of
corresponding web browser (para 0009) to collect data results from prescribed tasks associating said web-based testing interactions. Hence, configuring a test plan from a centralized setup (test suite - para 0008) to execute various client browser instances to carry out many iterations of the test plan in terms of prescribed test tasks and execution of test cases in parallel with respective entities linked under a voice calls flow/interaction (para 0032) is recognized.
Therefore, based on the number of test instances that can be repeated to a respective platform at different times, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement plural platforms for automating test execution instances under a common package build/layer in Magre so that the automated test distribution to multiple platforms is based on a centralized configuration that conceives or initiates a test plan - as in Kulkarni - to execute test case references in web application test case files set forth for a predefined number of iterations - as per Kulkarni use of a centralized plan; because
instantiation of test instances according to paradigm that distribute web-based test cases to
plural platforms as set forth above from a centralized and common test plan so that the execution
of test tasks or activities at a location can be iterated - as in Kulkarni - with repetitive instantiation of test packages as in Magre would increase likelihood that issues unaddressed by a given test run within the course of the testing paradigm can be resolved by subsequent runs, the distributed test plan mode enabling each test platform to operate as an isolated resource-wise runtime once the plan has been received into the platform, liberating the platform from having to coordinate with other platforms or the central service during each runtime of the distributed plan scheme, thereby enhancing the test throughput by the platform with respect to execution of tasks or functionalities prescribed by the received test plan, and so, in part due to the platform being able to carry out instructions or implementation of tasks using a simultaneous (parallel) execution mode that obviate synchronization linkage with any external, remote control entity so to only report results only after the test plan is fulfilled, the use of a centralized dispatch of a test plan enabling collected execution report from the testing at various platforms to be aggregated and analyzed centrally for issues, which in tum would enable a new test plan to be created to be iteratively passed back to the distributed test stream.
C) Nor does Magre explicitly disclose distributing test cases in parallel mode in terms of computer instructions to
spawn multiple threads to execute the web application test cases in parallel mode by leveraging capabilities of a multithreading framework
Concurrent execution of test tasks at a given platform runtime in Magre (para 0010, 0014) entails parallelization of code instances which would be best known as multi-threaded execution or implementation.
Similar to using plural virtual browsers as in Kulkarni to support concurrent test cases execution, Marullo, for instance, discloses a service to test web pages using manual or automated fashion, where verification of server application is conducted with test cases constructed from a definition file via a generation API (col. 7 li. 15-58) by employing virtual browsers (col .13 li. 35-43, li. 50-62), according to interactive users (Fig. 5) coupled with automated tool (Fig. 4- see Abstract) such as WebRunner or multiple instances thereof (Fig. 3; col. 13 li. 55-62) which implements simulation code with multi-threaded functionalities to simulate web browser activities as part of the test capabilities over web or server applications (col. 21 li. 5-42) according to which user-defined threads situated in a virtual browser are instantiated to test a transaction and log data (thread 100 begin execution simultaneously - for a Webstrain application, each transaction or test carried out as simultaneous thread actions as part of simulation (col. 21 li -60-62) and also logged with a API formed by a thread (col. 9-10). Hence use of multiple virtual browsers for web pages testing via test tools that include spawning multiple threads to execute the web application test cases in parallel mode by leveraging capabilities of a multithreading framework to test, simulate and log action result is recognized.
Therefore, it would have been obvious for one of ordinary skill in the art before the effective
filing date of the invention to implement software concurrent execution of test code in Magre with use of multi-platforms so that for a given platform, the application code under test would be instantiated under given test tools in form of multi-threaded implementation - as in Marullo – that spawns as needed one or more plurality of threads to perform a given web application test cases, mostly in parallel mode, the use of multi-threaded implementation including effect of leveraging capabilities of a multithreading framework such as evidenced in Marullo creating of threaded Webstrain via WebRunner tool; because
provision of testing capabilities according to a distributed testing paradigm where each platform destined to execute a test instance of web application data underlying a Web-based environment makes use of one or more user-created virtual browsers and is accommodated with a test tool as set forth in Marullo, would enable test code execution and data logging related therewith to use multi-threaded capability of the tool, the thread-implemented SW capability not only suiting the virtualization of a test environment in adhering to or optimizing the scope of resource afforded under one or more such virtual user browser created by under the whim or desire of platform user; but also enabling threads to be spawned by way of the test tool per a need-basis to accommodate payload demand of application data, test case task size, responding to actual or dynamic extent of application I/O, meeting the surge of request/response complexity or degree of inter-process interchanges underlying data and code calling included in web pages/applications being tested in accordance to the multi-platform distributed paradigm.
D) Nor does Magre explicitly disclose performance testing in terms of a computer configured to establish a performance baseline of an application by executing a predefined set of workflows under an expected load on a server to generate and measure one or more metrics directed to reliability, performance, and scalability.
In Magre, server can be part of platforms or hardware hosts (para 0034-0035) used as test tools to load and execute test cases comprising workflow components obtained from test case repository (repository 112, Fig. 1), with test results from such platforms returning and displaying test metrics (e.g. pass/fail performance) that are channeled to a test reporting manager for the overall consolidation (para 0051) of a status information on completion of test case or its atomics (para 0053), which is consistent with the test purpose of satisfying expectations relevant to standards of reliability of software under test (para 0001)
AbuAta discloses a management solution for a business corporation that implements change to planning, productivity, user satisfaction, efficiency, distribution, parallelism, workload balancing, traffic (para 0089) as well as utilization of server resources; for instance, to reprioritize CPU, I/O distribution and bottleneck (Table 1, para 0090), apply strategic benchmarking of the operational layers (para 0276) or processes to review underlying costs against benchmark standards (para 0301-0303) including benchmarking a service against a best service to determine where workloads should be positioned (para 0339-0342) as well as a mathematical model to monitor workloads and availability of resources (para 0111), by generating and analyzing stress to the business I/O, layers (para 0097) and reporting cases that match an acceptable business logic, including modifications to meet/arrive at the performance metrics (para 0113-0114) as measure to meet quality conformance of a service, the reliability thereof (para 0291-0292) or scalability requirements (para 0165), the reporting providing indication on throughput metrics, service quality, reliability and scalability (para 0116) as means to correlate business functions and/or business processes indicative of improving all levels of the corporation.
Hence, benchmarking a service for resources utilization, workload balancing, efficient redistribution of workloads to meet acceptable business logic, performance metrics or service quality and scalability to improve throughput of the service, balance out complexities of server resources and traffic bottlenecks entails effort to establish an acceptable operational baseline by benchmarking services or executing a model defining a set of workflows on server entities relative to an expected load to generate and measure one or more metrics directed to reliability, performance, and scalability
Conti also discloses test coverages to establish effectiveness of runtime workload distribution and optimization resources utilization (para 0038) via profiling and analytics (para 0043-0045; workload profiling – para 0060), using a test in conjunction with test execution workload (para 0053) as part of functional coverage and acquiring metrics that impact optimality of return on investment (ROI) on basis of workload run facts data, stress and activity levels and test effort within a test plan (para 0051), the effectiveness of test workload being achieved via measurement of metrics affording scalability performance (para 0065), reliability determination (para 0070) in form of performance indicators provided via benchmarks by industry, software and discipline standards (or deviation thereof) included in configuration of test workloads (para 0048-0049), environment, SW/HW, firmware operating in cloud compute, servers and problem discovery, defect identification systems (para 0070). Hence workload run and metrics obtained thereby indicative of efficiency in test coverage, expressed as performance indicators provided via benchmarking of server/cloud configuration by which to determine scalability and reliability of the workload test entails attempt to establish a performance baseline from benchmark/test metrics that are conducive to determination of reliability, performance, and scalability associated with configuration of workload runs implemented as test on cloud compute or servers.
Therefore, based on test case that include workflows whose execution results in test performance gathering in Magre, it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement management and consolidation of status information upon completion of test case or its atomics in Magre so that consolidation of a test efficiency respective to service standards and norms on performance would include establishing of a performance baseline for a service test by executing a predefined set of workflows or workload runs under an expected load on one or more servers – as per a service benchmarking in AbuAta - or a cloud service to generate and measure one or more metrics directed to reliability, performance, and scalability – as set forth above in the service benchmark by AbuAta, and workload test runs using server/cloud configurations in Conti; because
implementing test by applying set of workloads to a given service entity of a cloud compute environment as part of leveraging test coverage or benchmarking qualitative tests as set forth above, from which to collect execution metrics or performance data, would incrementally consolidate via iterative test application a standard of performance or service quality baseline in that multiple instances of servers can be submitted to stress-testing via an iterative coverage model - as set forth above in AbuAta or Conti – each test using different set of workload and conditioning scenario so that the performance result from each coverage can be correlated with data from other or previous cycle, filtered, retrained and reevaluated, in order for a most acceptable set of quality, performance metrics to be set as norm, standard or baseline, which in turn can be used as reference for other test comparison and evaluation, reducing thereby the inherent complexity (and resource utilization) problem associated with leveraging capabilities of a business network and seeking the best throughput or performance of the service as illustrated in Magre test infrastructure for satisfying expectations relevant to standards of reliability of software (e.g. service performance) under test, where test case considered most reliable or compliant to a baseline can be ingested to a standardized test data repository for subsequent reuse.
As per claim 2, Magre discloses system of Claim 1, wherein the mapping for the one or more web elements in an application are stored in different locations (atomic for finding a matching
elements (e.g. web object), atomic for finding location of an element - para 0026; map of key-value
pairs for test data ... identifying a first plurality of web objects ... from repository - claim 1, pg. 8; first map of key-value pairs for test data from the test data repository; second map of key-value pairs for test data from the ... repository - claim 1, pg.8; repository 111 - para 0022).
As per claim 3, Magre discloses system of claim 1, wherein the computer is further configured to: analyze each web application test case file (Fig. 2A, 2B) and corresponding properties file (test data 211 - para 0045; refer to rationale A of claim 1) to determine an appropriate external
testing component and an API call for each action (functionality ... operations for accessing the
URL ... Selenium may run a script ... retrieving the user ID and password from the test data - para
0032) required by each web application test case.
As per claim 4, Magre discloses system of Claim 1, wherein the computer is further configured to:
create the web application test case files (see rationale A) with a spreadsheet editing program (test data ... map of key value pairs ... in the test data repository ... test data and possibly other test cases may be stored ... in a spreadsheet file - para 0045 - Note3: structuring test cases and test data in a spreadsheet format in a pertinent repository reads on use of a spreadsheet editing module/UI/tool to create such spreadsheet file)..
As per claim 5, Magre discloses system of Claim 4, wherein the computer is further configured to:
associate the web application test cases with a URL (e.g. for testing login functionality may include ... uniform resource locator - para 0031) pointing to one or more application (URL of web
application 150 - para 0031) or web servers hosting a program being tested.
As per claim 8, Magre discloses a computer-implemented method for quality assurance and performance testing of supply chain applications and systems, comprising:
storing, by a database, one or more testing application programming interfaces and at
least one properties file comprising a map between a user interface element and its locator,
wherein the at least one properties file comprises identifying actual values for selector, value and
dataset elements, wherein the selector, value and dataset elements are stored as key=value pairs;
establishing. by the computer, a performance baseline of an application by executing a
predefined set of workflows under an expected load on a server to generate and measure one or
more metrics directed to performance, scalability and reliability;
configuring, by a computer, a test plan to execute test case references in web application
test case files for a predefined number of iterations and for a predefined number of concurrent
users;
providing, by the computer, a user interface for receiving the web application test case
files that describe one or more actions to be tested and properties files that each map one or more
elements to one or more values, wherein each properties file comprises a mapping between one
or more web elements and corresponding locator types and values;
translating, by the computer, received web application test case files and corresponding
properties files into web application test cases;
spawning, by the computer, multiple threads to execute the web application test cases in
parallel mode by leveraging capabilities of a multithreading framework; and
executing, by the computer, the web application test cases by identifying the one or more
actions identified in each web application test case and automatically invoking one or more
testing components configured to execute a test using the one or more actions.
(all of which having been addressed in claim 1)
As per claim 9, refer to claim 2.
As per claim 10, refer to claim 3
As per claims 11-12, refer to rejection of claims 4-5, respectively.
As per claim 15, Magre discloses a non-tangible[sic] computer-readable medium embodied with software, the software when executed configured to:
store, by a database, one or more testing application programming interfaces and at least
one properties file comprising a map between a user interface element and its locator, wherein
the at least one properties file comprises identifying actual values for selector, value and dataset
elements, wherein the selector, value and dataset elements are stored as key=value pairs;
establish a performance baseline of an application by executing a predefined set of
workflows under an expected load on a server to generate and measure one or more metrics
directed to performance, scalability and reliability;
configure a test plan to execute test case references in web application test case files for a
predefined number of iterations and for a predefined number of concurrent users;
provide a user interface for receiving the web application test case files that describe one
or more actions to be tested and properties files that each, maps one or more elements to one or
more values, wherein each properties file comprises a mapping between one or more web
elements and corresponding locator types and values;
translate a received web application test case files and corresponding properties files into
web application test cases;
spawn multiple threads to execute the web application test cases in parallel mode by
leveraging capabilities of a multithreading framework; and
execute the web application test cases by identifying the one or more actions identified in
each web application test case and automatically invoking one or more testing components
configured to execute a test using the one or more actions.
(All of which having been addressed in claim 1)
As per claims 16-17, refer to rejection of claims 2-3, from above
As per claims 18-19, refer to rejection of claims 4-5.
Claims 6-7, 13-14, 20 is/are rejected under § 35 U.S.C. 103 as being unpatentable over Magre et al, USPubN: 2018/0137035 (herein Magre) in view of Kulkarni et al, USPubN: 2017/0220459 (herein Kulkamy), Marullo et al, USPN: 6,185,701 (herein Marullo) and Tammariello et al, USPubN: 2019/0065353 (herein Tammariello) further in view of Abu El Ata USPubN: 2012/0197686 (herein AbuAta) and Conti et al, USPubN: 2018/0067844 (herein Conti) and further of Terry et al, USPubN: 2016/0027198 (herein Terry)
As per claims 6-7, Magre does not explicitly disclose system of Claim 1,
wherein a web application test case comprises a comma separated variable input comprising action type, selector, value and dataset.
wherein the selector specifies an attribute name used to locate a web element.
Similar to Magre using a logical locator attribute in processing key-pair structure associated with forming a test (e.g. on login functionality) of a web-based application, Terry discloses a script
that comprises a operator connecting consecutive actions (para 0459-0460) including in a control clause, where as part of data associated with the actions, a choice operator (para 0461) included with the script data (para 0371-0373; variable name ... next to the choice operator - para 0375) and operating as logic for effecting a choice text based on a user-selected input - name or a variable - as part of dynamically processing a external meta-language file for assembling graphical elements (e.g. variable name, value - para 0377) associated with conversion of the script from said meta-language (para 0027), where one such script can be adapting a JSON, or CSV format (para 0060-0061, 0065; para 0190-0191), whereby JSON, CSV fields corresponding to characters, nodes of web pages (para 0463), data, functionalities of a script (e.g. interactive features, logic to evaluate A/B test variables ... via CSV files corresponding to the A/B test script - para 0438) enable an field interpreter to perform rendering, accessing of data or translating a definition from a CSV format associated with (para 0079) automating a test component (para 0084; step 408, 410 - Fig. 4) as terms of script interactions functionalities such as rendering, selecting, testing (component 312 - Fig. 3) and logging (para 0071-0072) or making references to web pages (claim 19, pg. 29-30);
Hence, assembling logic of a script with paired actions, choice/selection operator and variable values, references to a web page nodes/characters from a CSV structure in Terry discloses including with formation of a test case, a comma separated variable input comprising action type,
selector, value and dataset, where the selector specifies an attribute name used to locate a web element.
Therefore, based on use of key-value pair mapping in a properties file in Magre (refer to rationale A from claim 1) to assemble a test case in conjunction with web object repository and test atomics (para 0053) to find or locate an external variable or web element (name or email address, actual password - para 0045), it would have been obvious for one of ordinary skill in the art before the effective filing date of the invention to implement formation or assembly of test functionalities using the test case builder in Magre for testing a web application so that one such web application test case would comprise a specification and/or definition of elements, variable, text and actions and
external features formatted with (or structured from) a comma separated variable provided as input - as in Terry - into the test case to respectively represent an action type, selector, value and dataset; wherein the selector specifies an attribute name used to locate a web element - as set forth in Terry; because
structuring definition information, actions, variable or externally retrievable data or file in a
structure format such as JSON language, or as a simply a CSV file as set forth above would facilitate extension of the information or features defined in this simple file format, which not only requires a limited amount resources for their structuring, editing and storing but would also benefit from how information structured in this format can be easily ingested, exported, expanded or edited and stored without undue cost to maintenance resources; e.g. the comma separated format facilitating parsing, retrieval and extraction, modification, augmentation, reduction and restoring for reuse into another environment; which in tum would mitigate extra-enlisting of resources by a test case configuration context as endeavored in Magre' s web-based application test build, necessarily when the iterative aspect of concurrent platforms employed for a distributed test paradigm in Magre requires multitude type of functions, web elements, HTTP and internet identification, network variables, and communication 1/O parameters to be accounted for along with environment constraints of host platform, real-time dependencies and inter-relationship thereof with state of the NW, communication traffic in forming the needed test functionalities to be deployed, in the sense that simple file formation of test file such via a CSV format affording simplistic editing, manipulation and ease in storage maintenance as set forth above can significantly alleviate test configuration effort in regard to considering size of data, type of logic and parameters to seek and select for the web testing.
As per claims 13-14, refer to rationale of claims 6-7 from above.
As per claim 20, refer to rejection of claim 6 from above.
Response to Arguments
Applicant's arguments filed 11/24/25 have been fully considered but they are not persuasive. Following are the Examiner’s observations in regard thereto.
(A) Applicants have submitted that Magre, (notably in terms of spreadsheet) is silent or without hint in regard to a “properties file” that comprise “a map between a user interface element and its locator … identifying actual values for selector … the selector, value and dataset elements are stored as key=value pairs” (Applicants Remarks pg. 11, middle)
The rejection has shown that a key=value pair is part of a configuration file in Magre while obviousness of using a file format to store this key=value pair structure is demonstrated with teachings from Tammariello via use of a markup structure.
Demonstration on non-obviousness of a feature cannot be persuasive if the rebut against the obviousness rationale in question solely discusses deficiencies on one reference taken separately from the other references utilized in the combination proffered by one skill in the art in presenting the obviousness rationale. In fact, the rebut by Applicants appears silent about analyzing and discussing merits of the prongs of the Office Action 103 rationale that combines Tammariello file format with the key=value pair configuration properties by Magre. Thus, the prima-facie merits of the non-obviousness for this “properties file” feature is largely inconclusive.
(B ) Applicants have submitted that Magre fails to teach or suggest “establish a performance baseline by executing … workflows under expected load on a server to … measure one or more metrics directed to performance, scalability and reliability” language in the current Amendment (Applicants Remarks pg. 11, bottom)
Raise of patentability merits in regard to a newly added feature is deemed largely MOOT in view of the adjusted grounds of rejection that has been necessitated by this amendment.
In all, the claims presented with the latest Applicant response will stand rejected as set forth above.
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Tuan A Vu whose telephone number is (571) 272-3735. The examiner can normally be reached on 8AM-4:30PM/Mon-Fri.
If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor, Chat Do can be reached on (571)272-3721.
The fax phone number for the organization where this application or proceeding is assigned is (571) 273-3735 ( for non-official correspondence - please consult Examiner before using) or 571-273-8300 ( for official correspondence) or redirected to customer service at 571-272-3609.
Any inquiry of a general nature or relating to the status of this application should be directed to the TC 2100 Group receptionist: 571-272-2100.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
/Tuan A Vu/
Primary Examiner, Art Unit 2193
Decembre 31, 2025