Get the App
SLTechnology News&Howtos  ›  Internet Technology  › 

Improvement plan for project automation test architecture-remove action instructions

Shulou Source: shulou.com Published: 2022-06-03 07:07:00 09月21日 Update

Because we define multiple action instructions in test_suite.xml, for example, they instruct us to Engine to operate on the final data, these action instructions are not data, so they are not included in our final data result set, so we have to remove them. So we use the following code to do the removal:

Public class XMLManipulator {public static String removeModifyConfFromXML (String xmlString) throws Exception {Document doc = null; doc = DocumentHelper.parseText (xmlString); / / remove the from the target xml List addPart = doc.selectNodes ("/ test_suite/test_case/add_elements"); for (Node node: addPart) {node.getParent () .remove (node) } / / remove the from the target xml List updatePart = doc.selectNodes ("/ test_suite/test_case/update_elements"); for (Node node: updatePart) {node.getParent () .remove (node) } / / remove the from the target xml List removePart = doc.selectNodes ("/ test_suite/test_case/remove_elements"); for (Node node: removePart) {node.getParent () .remove (node);} / / find document again return doc.asXML () }..}

The final xml file does not contain code snippets for these action instructions.

Tags: Actions instructions data code multiple instructions files fragments for results work architecture project testing automation Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Microsoft MariaDB OPPO Reno Apple vpn