Package de.hybris.platform.ticket.jalo
Class TicketServiceScenariosTest
java.lang.Object
de.hybris.platform.testframework.HybrisJUnit4Test
de.hybris.platform.servicelayer.ServicelayerBaseTest
de.hybris.platform.servicelayer.ServicelayerTest
de.hybris.platform.servicelayer.ServicelayerTransactionalTest
de.hybris.platform.ticket.jalo.AbstractTicketsystemTest
de.hybris.platform.ticket.jalo.TicketServiceScenariosTest
- All Implemented Interfaces:
JaloSessionHolder
Test Case that tests some business meaningful scenarios.
Scenario 1: - Ticket is created as a result of a call by a customer, reporting a issue. - Ticket is moved to the Open
status - A Note is added to the Ticket as a result of some action taking to resolve the issue. - The Ticket is
closed.
Scenario 2: - A customer calls regarding a currently open ticket - The ticket is found via the reference provided by
the customer - A Note is added to the Ticket recording the additional call
Scenario 3: - An email is received and a new ticket is created as a result - Customer is called regarding the
email/ticket - Ticket closed as a result of the call
Scenario 4: - A customer calls regarding a previously closed ticket - The ticket is found via the reference provided
by the customer - Ticket is reopened
Scenario 5: - A customer calls regarding a undelivered item on their order - A ticket is raised against the order -
The Ticket status is updated to Open - Ticket is assigned to an Agent
Scenario 6: - Problem Ticket Scenario, Ticket is raised and then bounced around. Nothing is resolved. Real World of
Call Centres.
-
Nested Class Summary
Nested classes/interfaces inherited from class de.hybris.platform.ticket.jalo.AbstractTicketsystemTest
AbstractTicketsystemTest.MockTicketEventEmailStrategy -
Field Summary
Fields inherited from class de.hybris.platform.ticket.jalo.AbstractTicketsystemTest
adminUser, i18nService, testGroup, testUser, ticketBusinessService, userServiceFields inherited from class de.hybris.platform.servicelayer.ServicelayerTest
importServiceFields inherited from class de.hybris.platform.testframework.HybrisJUnit4Test
jaloSession -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoidsetUp()voidtearDown()voidScenario 1: - Ticket is created as a result of a call by a customer, reporting a issue.voidScenario 2: - A customer calls regarding a currently open ticket - The ticket is found via the reference provided by the customer - A Note is added to the Ticket recording the additional callvoidScenario 3: - An email is received and a new ticket is created as a result - Customer is called regarding the email/ticket - Ticket closed as a result of the callvoidScenario 4: - A customer calls regarding a previously closed ticket - The ticket is found via the reference provided by the customer - Ticket is reopenedvoidScenario 5: - A customer calls regarding a undelivered item on their order - A ticket is raised against the order - The Ticket status is updated to Open - Ticket is assigned to an AgentvoidScenario 6: - Problem Ticket Scenario, Ticket is raised and then bounced around.voidThis is a sample test method.Methods inherited from class de.hybris.platform.servicelayer.ServicelayerTest
createCoreData, createDefaultCatalog, createDefaultUsers, createHardwareCatalog, getApplicationContext, importCsv, importData, importData, importData, importStream, importStream, isPrefetchModeNoneMethods inherited from class de.hybris.platform.servicelayer.ServicelayerBaseTest
autowireProperties, getBeanName, prepareApplicationContextAndSessionMethods inherited from class de.hybris.platform.testframework.HybrisJUnit4Test
establishJaloSession, finish, getOrCreateCurrency, getOrCreateLanguage, init, intenseChecksActivated, takeJaloSession
-
Constructor Details
-
TicketServiceScenariosTest
public TicketServiceScenariosTest()
-
-
Method Details
-
setUp
- Overrides:
setUpin classAbstractTicketsystemTest- Throws:
Exception
-
tearDown
public void tearDown() -
testTicketServiceScenarios
public void testTicketServiceScenarios()This is a sample test method. -
testScenario1
public void testScenario1()Scenario 1: - Ticket is created as a result of a call by a customer, reporting a issue. - Ticket is moved to the Open status - A Note is added to the Ticket as a result of some action taking to resolve the issue. - The Ticket is closed. -
testScenario2
public void testScenario2()Scenario 2: - A customer calls regarding a currently open ticket - The ticket is found via the reference provided by the customer - A Note is added to the Ticket recording the additional call -
testScenario3
public void testScenario3()Scenario 3: - An email is received and a new ticket is created as a result - Customer is called regarding the email/ticket - Ticket closed as a result of the call -
testScenario4
public void testScenario4()Scenario 4: - A customer calls regarding a previously closed ticket - The ticket is found via the reference provided by the customer - Ticket is reopened -
testScenario5
public void testScenario5()Scenario 5: - A customer calls regarding a undelivered item on their order - A ticket is raised against the order - The Ticket status is updated to Open - Ticket is assigned to an Agent -
testScenario6
public void testScenario6()Scenario 6: - Problem Ticket Scenario, Ticket is raised and then bounced around.
-