Break test dependencies

In the ideal unit test setup, we want to eliminate external behaves from our target test. For example, suppose we want to add a test for functionX; inside this function, we call functionY from a different file. In this scenario, we should try to mock functionY. Unfortunately, this is not the case in the kw code, and it represents a huge technical deficit for the project. We need to refactor our tests at some point, but let's register this critical task as an Epic to someone else work in the near future.

Acceptance Criteria:
Expand our documentation to describe how to mock functions.
Create a milestone that has an issue per test with this dependency problem.

P.s.: Ideally, we want to fix this issue before releasing version 1.0.

Start by identifying kw tests whose target functions call external functions, since no specific files or tests are named. Document how to mock functions, then create a milestone with one issue for each test dependency problem; completion means the guidance and issue breakdown exist.