From a360c8f2809d90f5c1893fcbdf6c9e2d102ff8b6 Mon Sep 17 00:00:00 2001 From: debugtalk Date: Thu, 30 Jul 2020 13:45:01 +0800 Subject: [PATCH] docs: add concept of debugtalk.py --- docs/user/concepts.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/user/concepts.md b/docs/user/concepts.md index e74b202d..a7c32fdd 100644 --- a/docs/user/concepts.md +++ b/docs/user/concepts.md @@ -1,4 +1,11 @@ +## debugtalk.py + +Based on the philosophy of `Convention over configuration`, each project should and could only have one `debugtalk.py` file. This file has multiple functions. + +- As the root path anchor of the project, the relative paths in testcase, such as referencing testcases or CSV files, are all based on this root path +- Store custom python functions, the functions called in the testcase are all defined in this file + ## variables priority There are several different types of `variables`, and the priory can be confusing. The best way to avoid confusion is to use different variable names. However, if you must use the same variable names, you should understand the priority strategy.