Converters usage

[dtamajon]

I'm starting to use easytest, and I'm trying to use Converters to load entities in my test classes. After reading documentation, I don't know how to solve following situation:

I have methodA and methodB in my TestCase class, and both requires an Item entity to work. I can get entity with Converter, but how can I use a different set of Items for each method? I guess with TestMethod in my xml data file?

Furthermore, Item has a property Provider, which is an entity too. How should I define the information to load? Just as InputData entries and maganed in my Converter?

And finally, when Item has a property of type List , how should I store data in the XML to be properly read?

Thanks!

[anujgandharv]

Hi,
Can I ask if you are using easytest-core library and if yes then which version?

So lets take your problem statements one by one:

1. Two tests methods taking the same Class Object but different instances.
   You can use the same class(in your case Item), for different test methods. All you have to do is define the data for each method separately in the XML under TestMethod. So here is an example XML file where two methods methodA and methodB both use the Item object:

<easytest:InputTestData xmlns:easytest="urn:org:easetech:easytest:1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:org:easetech:easytest:1.0 testDataSchema.xsd">

Also note that if your Item class has a no-arg constructor, then EasyTest will automagically convert the test data into an Item class and you dont have to write any converters yourself. The only thing you have to make sure is that the name of attributes in XML file match the name of the variables defined in the Java POJO class.

1. Handling property Provider. Ideally if you use Excel and CSV then you can provide a JSON object of any depth and EasyTest will convert it into a proper Java class. You can try providing JSON in an XML file but I do not remember it from the back of my head whether JSON functionality is availabe for XML data loader or not. If that is not feasible, then you can define the properties inside Provider class in your XML and handle it in your Converter implementation, as you already said in your email.
2. Property of type list: If the List is of basic type (String, Integer/int, Long/long etc), then all you have to do is provide them as comma-separated list in your XML file and EasyTest will take care of properly converting the comma separated list to the list type in Java object. If it is of Complex Type, then you have to define your own constructor and handle it yourself.

Hope I have been clear.
Do let me know if you need more information.

Thanks,
Anuj Kumar

[anujgandharv]

Well, looks like Github removed my XML
I will try to send you a gist.

[anujgandharv]

Here is the XML for the above use case : https://gist.github.com/anujgandharv/dd393be0475b0d4bd206

[dtamajon]

Thank you for the fast answer Anuj.

If object depth is not supported in XML, I will use JSON (I prefer one way instead of mixing).

And, just another dubt: can I define more than one TestMethod at a time to share TestRecords, something like <TestMethod name="methodA,methodB"> ?

[anujgandharv]

Hi,
I do not understand your last doubt. Do you mean to say that is there a way to define some sort of global values for each test method. If that is the question than the answer is unfortunately no. But you can provide default values for each test record within a given test method. I hope that helps.

[dtamajon]

Hi,

No. I refer if there is a way to share more than one InputData between different test methods.

I'd like to define something like:

<TestMethod name="getItemsData,getMoreItemsData">
 <Description>The method with name GetItemsData and getMoreItemsData will be executed 3
   times by the EasyTest framework,
   once each for the given TestRecord.
 </Description>
 <TestRecord id="1">
  <Description>This test tries to capture the scenario when the data is
    available in the DB
    for the given set of input parameters. In this
    case the expectedItems
    should be 2.
  </Description>
  <InputData>
   <Entry key="itemId" value="2600" />
   <Entry key="itemType" value="book" />
   <Entry key="expectedItems" value="2" />
  </InputData>
 </TestRecord>
 <TestRecord id="2">
  <Description>This test tries to capture the scenario when the data is
    available in the DB
    for the given set of input parameters. In this
    case the expectedItems
    should be 1.
  </Description>
  <InputData>
   <Entry key="itemId" value="3600" />
   <Entry key="itemType" value="journal" />
   <Entry key="expectedItems" value="1" />
  </InputData>
 </TestRecord>
 <TestRecord id="3">
  <Description>This test tries to capture the scenario when the data is
    available in the DB
    for the given set of input parameters. In this
    case the expectedItems
    should be 0.
  </Description>
  <InputData>
   <Entry key="itemId" value="4000" />
   <Entry key="itemType" value="ebook" />
   <Entry key="expectedItems" value="0" />
  </InputData>
 </TestRecord>
</TestMethod>

[anujgandharv]

Hi,
unfortunately EasyTest does not have this sort of mechanism.
But a workaround would be to take the existing XMLLoader that Easytest has and extend the code to suit your need and then give this Custom written loader to your test method. Easytest will then do the right thing for you.

I hope it helps. Let me know if you have more questions.

Thanks,
Anuj