Blazemeter / taurus

Compare 27dd542 ... +0 ... ceff890

No flags found

Use flags to group coverage reports by test type, project and/or folders.
Then setup custom commit statuses and notifications for each flag.

e.g., #unittest #integration

#production #enterprise

#frontend #backend

Learn more about Codecov Flags here.

Showing 1 of 2 files from the diff.

@@ -23,7 +23,7 @@
Loading
23 23
from bzt.engine import HavingInstallableTools
24 24
from bzt.modules import SubprocessedExecutor
25 25
from bzt.modules.services import PythonTool
26 -
from bzt.utils import RequiredTool
26 +
from bzt.utils import RequiredTool, CALL_PROBLEMS
27 27
from bzt.utils import get_full_path, RESOURCES_DIR
28 28
29 29
@@ -118,6 +118,18 @@
Loading
118 118
    def __init__(self, engine, version, **kwargs):
119 119
        super(Robot, self).__init__(packages=["robotframework", "apiritif"], version=version, engine=engine, **kwargs)
120 120
121 +
    def check_if_installed(self):
122 +
        self.log.debug(f"Checking {self.tool_name}.")
123 +
        try:
124 +
            _, _ = self.call([sys.executable, "-m", self.tool_name.lower(), "--version"])
125 +
        except CALL_PROBLEMS as exc:
126 +
            if exc.returncode == 251:
127 +
                self.log.debug(f"{self.tool_name} output: {exc.stdout}")
128 +
                return True
129 +
130 +
            self.log.debug(f"{self.tool_name} check failed: {exc}")
131 +
            return False
132 +
121 133
122 134
class TaurusRobotRunner(RequiredTool):
123 135
    def __init__(self, tool_path, **kwargs):

Everything is accounted for!

No changes detected that need to be reviewed.
What changes does Codecov check for?
Lines, not adjusted in diff, that have changed coverage data.
Files that introduced coverage data that had none before.
Files that have missing coverage data that once were tracked.
Files Coverage
bzt -0.02% 90.43%
Project Totals (69 files) 90.43%
Loading