Notes on variables captured in test closures (#268)

* Added notes on variables captured in test closures

* Apply suggestions from code review

Co-authored-by: kazk <kazk.dev@gmail.com>

* Apply suggestions from code review

Co-authored-by: kazk <kazk.dev@gmail.com>

Co-authored-by: kazk <kazk.dev@gmail.com>

Author: hobovsky

content/languages/javascript/authoring.md

@@ -105,6 +105,7 @@ describe("Generated test cases", () => {
 
 This technique is liked by authors familiar with testing frameworks that provide parameterized or generated test cases out of the box, like NUnit or JUnit. However, some caution is needed when this approach is used. Test suites organized like this can become large and can flood the test output panel with many entries, making it unreadable or causing performance problems in client browsers.
 
+
 ### Chai
 
 JavaScript kata should use [Chai](https://www.chaijs.com/) as the assertion library.

content/languages/python/codewars-test/index.md

@@ -41,6 +41,8 @@ This is a convention used in many Python kata, but it's not a requirement, and a
 
 Tests in the Python testing framework are composed of functions decorated with a set of Python decorators. All such functions are automatically discovered and run. The final result for every test block is determined by contained assertions and reported along with its measured execution time.
 
+Test decorators call the functions immediately, so it's safe to use them in a loop.
+
 
 ### Test groups: `@test.describe`