> The point is not how to write assertions, but how to replace
implementation of compoteGraph
> with some other that would return something else for sake of testing only
one module instead of all deeply dependant modules.

What do you mean by "replace implementation"?

Are you trying to verify if `compoteGraph` returns what you are expecting
the function to return?

If that is the case, how do you know what `compoteGraph` is expected to
return in the first instance?

In general, it is not possible to predict the return value of a function
without executing the function.

On Tue, Jul 2, 2019 at 3:15 PM Adam Eisenreich <akxe at seznam.cz> wrote:

> The point is not how to write assertions, but how to replace
> implementation of `compoteGraph` with some other that would return
> something else for sake of testing only one module instead of all deeply
> dependant modules.
>
> I suppose that the user gesture might be solvable by starting browser with
> correct configuration. It isn't the easy plug-play style that javascript
> usually have, but that might be fine, as this isn't the most typical use
> case anyway.
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20190702/7f11dd9a/attachment.html>

> The point is not how to write assertions, but how to replace implementation of compoteGraph
> with some other that would return something else for sake of testing only one module instead of all deeply dependant modules.

What do you mean by "replace implementation"?

Are you trying to verify if `compoteGraph` returns what you are expecting
the function to return?

If that is the case, how do you know what `compoteGraph` is expected to
return in the first instance?

In general, it is not possible to predict the return value of a function
without executing the function.