es.upm.dit.gsi.beast.reader.mas
Class CreateMASTestCase

java.lang.Object
  es.upm.dit.gsi.beast.reader.mas.CreateMASTestCase

public class CreateMASTestCase
extends Object

Main class to create the java file that controls each Test. First it will SETUP the scenario, then it will perform LAUNCH anything needed, and finally it will VERIFY the result. The code is the same for each TEST, but we must write one for each .story due to our BDD Tool (JBehave).

Author:

Alberto Mardomingo, Jorge Solitario

Constructor Summary

CreateMASTestCase()

Method Summary

static void

createBeastTestCase(String scenario_name, String platform_name, String package_path, String dest_dir, String loggingPropFile, String givenComment, String whenComment, String thenComment, String storyName, String story_agent, String agent_feature, String agent_benefit) Method to create the java file that it's executed from caseManager.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CreateMASTestCase

public CreateMASTestCase()

Method Detail

createBeastTestCase

public static void createBeastTestCase(String scenario_name,
                                       String platform_name,
                                       String package_path,
                                       String dest_dir,
                                       String loggingPropFile,
                                       String givenComment,
                                       String whenComment,
                                       String thenComment,
                                       String storyName,
                                       String story_agent,
                                       String agent_feature,
                                       String agent_benefit)
                                throws BeastException

Method to create the java file that it's executed from caseManager. Its name comes from the Scenario that it's testing. Its behaviour is written in the .story file allocated in the same folder, which is the plain text given by the client.

Parameters:

scenario_name - the name of the Scenario

platform_name - the agent platform in usage (i.e. jade or jadex)

package_path - the package containing the tests

dest_dir - the main folder main (typically src/main/java)

logginfPropFile - the path to the logging properties file

givenComment - the GIVEN part of the scenario

whenComment - the WHEN part of the scenario

thenComment - the THEN part of the scenario

Throws:

BeastException