4. Push robotframework execution results to MySQL

In this section we will discuss on how to push execution results to MySQL (which is used by rfhistoric)

---

Robotframework Historic report required following information, users must pass respective info while using parser

-o --> output.xml file name
-s --> mysql hosted machine ip address (default: localhost)
-u --> mysql user name (default: superuser)
-p --> mysql password (default: passw0rd)
-n --> project name in robotframework historic
-e --> execution info
-g --> ignore execution results. Helps when dont want to include results in mysql (default: False)
-f --> Include full suite name (default: False)

• Use robotframework-historic-parser to parse output.xml's

  > rfhistoricparser
   -o "<OUTPUT.xml FILE>"
   -s "<SQL_HOSTED_IP>"
   -u "<NAME>"
   -p "<PWD>"
   -n "<PROJECT-NAME>"
   -e "<EXECUTION-INFO>"
  

Note: Here if MySQL hosted in:

• Local Machine then use localhost Ex: -s localhost
• Remote Machine then use ipaddress Ex: -s 10.30.2.150 - > If -s 10.30.2.150 doesn't work try -s 10.30.2.150:3306

Example:

> rfhistoricparser -o "output1.xml" -s "10.30.2.150" -u "admin" -p "Welcome1!" -n "project1" -e "Smoke test on v1.0"

---

Ignore execution results

• You may get scenarios where you dont want to include current execution in mysql then use flag -g or --ignoreresult as follows:

rfhistoricparser -g "True"

Above flag will terminate storing results into mysql

Example: You have Jenkins job where rfhistoricparser executes after every build, -g helps here to avoid storing results into mysql