[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ] Stetson Robinson edited comment on DROOLS-2706 at 7/9/18 1:39 PM: ------------------------------------------------------------------ I agree with [~uxdlc]. Cucumber's term is even more confusing. [~ibek], you say "I'd like to get a simulation word in there to tell that the tool is not just for testing but also for simulating in various environments...etc." I don't know what you mean. Why else would you simulate a scenario except to test that the assets involved function as expected? To me, a scenario is only for testing. What's a non-testing use case for `.scenario` files? Here's the user's workflow: In a `.scenario` file, I create one or more scenarios involving given facts or conditions and expected outcomes as a result, based on my assets I've created (rules, DMN models, processets, whatever). Then I click "Run Scenario" (or whatever we want to call it) to validate that my assets involved in this scenario function as expected. So I created a scenario and I ran it. Is that it, in a nutshell? If so, to me, that's a method to test assets by using a defined scenario, a.k.a., a *Test Scenario*. I'm certainly open to other suggestions, but still don't see another use case for scenarios other than testing in one form or another. [~tirelli], [~Rikkola], adding you in case you have any insight on this naming discussion. was (Author: stetson.robinson): I agree with [~uxdlc]. Cucumber's term is even more confusing. [~ibek], you say "I'd like to get a simulation word in there to tell that the tool is not just for testing but also for simulating in various environments...etc." I don't know what you mean. Why else would you simulate a scenario except to test that the assets involved function as expected? To me, a scenario is only for testing. What's a non-testing use case for `.scenario` files? Here's the user's workflow: In a `.scenario` file, I create one or more scenarios involving given facts or conditions and expected outcomes as a result, based on my assets I've created (rules, DMN models, processets, whatever). Then I click "Run Scenario" (or whatever we want to call it) to validate that my assets involved in this scenario function as expected. So I created a scenario and I ran it. Is that it, in a nutshell? If so, to me, that's a method to test assets by using a defined scenario, a.k.a., a *Test Scenario*. I'm certainly open to other suggestions, but still don't see another use case for scenarios other than testing in one form or another. -- This message was sent by Atlassian JIRA (v7.5.0#75005)