Quark integration improvement

[pulorsok]

Describe the feature

Hi, @Surendrajat,
We (me, @18z, @krnick) have fixed a problem and implemented a feature:

1. Fix the Quark execution problem
2. Add reference treemap graph

Changes in this PR:

• Cd to project directory before executing quark to avoid permission error when quark logfile creates at root dir
• Add a feature that generates a quark reference treemap graph
• Add a button in the Quark report to show reference treemap graph

Future work

• Fix Quark execution problem on Windows platform
• Add unit test for the treemap feature

[Surendrajat]

@pulorsok thanks for the PR. I tested it briefly and noted that opening smali functions from the report somehow does not work for me. Did you try that?
Also, I believe we can't merge it until the windows issue is resolved so maybe make it as draft for now.

Some notes:

• graphviz is a hard dependency of Quark-Engine
• Windows tests are failing even on master
• We're using yarn instead of npm

[pulorsok]

Hi, @Surendrajat
Sorry for taking so long to respond.
I try to solve the problem by editing the execute cmd for Windows and testing on three platforms (Linux, OSX, Windows). Each platform is tested well locally (using npm test). Unfortunately, it seems the Travis CI still does not work. So could you provide some log messages to help me solve the problem? Thank you :)

[Surendrajat]

@pulorsok I'm seeing this error with all failing tests:

AssertionError [ERR_ASSERTION]: Analysis Report file /home/runner/work/APKLab/APKLab/testdata/simplekeyboard/test/quarkReport.json not found!

Seems like the output quarkReport.json file is not being detected. See if you can verify if it's there during test somehow or I'll do it when I get time.

We're using GitHub actions and all CI code is in https://github.com/APKLab/APKLab/blob/master/.github/workflows/apklab.yml file.

Also, although not much different but we're using yarn instead of npm now.

[Surendrajat]

@pulorsok I've fixed all issues with master branch and rebased your PR on it. I have also added a simple quark run step before actual tests on CI to simplify error debugging. Example run logs

[pulorsok]

@Surendrajat sorry for the late response, I will fix the problem ASAP.
And thanks for the kind help 😄