<commit_before>Feature: Extending a configuration with type discriminators
	As a user I want to be able to use simple functions in my modules
	So I can extend it without creating a grunt-task every time

Scenario: Call a function from a grunt task
	Given I have a src directory with a file "test.js"
	And I have an empty target directory
    Given I have a file "function.js" with the following content
    """
function rename(dest, src) {
    return dest + "/result.txt";
}
exports.rename = rename;
    """
    Given I have an empty build file
		And the build has the build steps "deploy"
			And the build step "deploy" has a task group "files"
				And the task group "files" in the build step "deploy" has a task runner that copies the src directory to the target directory and calls the function "rename" from script "function.js"
    And the build file is in the root of my application
    When I execute a custom build command with argument "--verbose"
    When I execute a custom build command with argument "--verbose"
    Then the file "result.txt" should exist in folder "target"
    <commit_msg>Again cucumberjs runners becoming instable on jenkins ci...<commit_after>Feature: Extending a configuration with type discriminators
	As a user I want to be able to use simple functions in my modules
	So I can extend it without creating a grunt-task every time

Scenario: Call a function from a grunt task
	Given I have a src directory with a file "test.js"
	And I have an empty target directory
    Given I have a file "function.js" with the following content
    """
function rename(dest, src) {
    return dest + "/result.txt";
}
exports.rename = rename;
    """
    Given I have an empty build file
		And the build has the build steps "deploy"
			And the build step "deploy" has a task group "files"
				And the task group "files" in the build step "deploy" has a task runner that copies the src directory to the target directory and calls the function "rename" from script "function.js"
    And the build file is in the root of my application
	When I execute the build command
	When I execute the build command
	When I execute the build command
    Then the file "result.txt" should exist in folder "target"
    
{'fraction_non_alphanumeric': 0.05175517551755175, 'fraction_numerical': 0.0, 'mean_word_length': 3.555327868852459, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7481433', 'n_tokens_mistral': 597, 'n_tokens_neox': 571, 'n_words': 349}