abouttutorialspricingterms
Login

  • Quick start
  • Modelling and data generation (part 1)
  • Modelling and data generation (part 2)
  • Integration with Java
  • Integration with C++
  • Integration with C#
  • Integration with Python
  • Integration with Node.js
  • Examples

Documentation

  • JUnit runner
  • Export templates

Modelling and data generation, part 1

Contents

Prerequisites and syntax
Model editor
Classes and methods
Parameters and choices
Hierarchical choices
Randomized choices
User types
Constraints
Data generation
Data export

Prerequisites and syntax

EcFeed was initially created to support model based testing of Java code. After a while the connections with Java were tightened, but to show the maximum of the ecFeed's functionality, we will assume that the model represents a Java project. Thus, we assume basic understanding of the Java code organization (packages, classes) and the syntax (naming rules, types).

All variable names must begin with a letter of the alphabet, an underscore ( _ ), or a dollar sign ( $ ). The convention is to always use a letter of the alphabet. The dollar sign and the underscore are discouraged.

After the first initial letter, variable names may also contain letters and the digits 0 to 9. No spaces or special characters are allowed.

The name can be of any length, but don't get carried away. Remember that you will have to type this name.

Uppercase characters are distinct from lowercase characters. Using ALL uppercase letters are primarily used to identify constant variables. Remember that variable names are case-sensitive.

You cannot use a Java keyword (reserved word) for a variable name.

Tip: Some programmers use underscore in variable names to separate parts of the name, such as shipping_weight. Others prefer a "capital style" notation, such as shippingWeight to separate parts of the name. NEVER use uppercase for every letter in a variable name, because uppercase names are reserved for final (constant) variables.



Samples of acceptable variable names: YES Samples of unacceptable variable names: NO
Grade Grade(Test)
GradeOnTest GradeOnTest#1
Grade_On_Test 3rd_Test_Grade
GradeTest Grade Test (has a space)