Skip to content

Latest commit

 

History

History
75 lines (55 loc) · 2.44 KB

README.md

File metadata and controls

75 lines (55 loc) · 2.44 KB
Raw

XML Content Parser Exercise

Imports data from text received via an API endpoint.

Installation

Xml.Content.Parser requires Visual Studio 2017 and .NET Core SDK 2.1+ to run.

Once installed:

Run the solution /Server/Xml.Content.Parser.sln in Visual Studio 2017
Once the solution has loaded, Press F5 to build and run the API in an IIS Express instance
Navigate to http://localhost:{port}/swagger to begin using the API

Note: The {port} number will be randomly assigned by Visual Studio.

Tech

This repository utilizes the following dependencies.

  • [ASP.NET Core 2.1] - Web Framework
  • [Autofac] - Dependency Injection
  • [Newtonsoft.Json] - JSON serializer/deserializer
  • [NUnit] - Testing framework
  • [FluentAssertions] - Test assertions using fluent syntax
  • [NSubstitute] - Mocking library

Exercise Instructions

The data received via the API will either be:

  • Embedded as islands of XML-like content
  • Marked up using XML style opening and closing tags

The following text illustrates this:

Hi Yvaine,

Please create an expense claim for the below. Relevant details are marked up as requested…

<expense>
    <cost_centre>DEV002</cost_centre>
    <total>1024.01</total>
    <payment_method>personal card</payment_method>
</expense>

From: Ivan Castle
Sent: Friday, 16 February 2018 10:32 AM
To: Antoine Lloyd <[email protected]>
Subject: test

Hi Antoine,

Please create a reservation at the <vendor>Viaduct Steakhouse</vendor> our
<description>development team’s project end celebration dinner</description> on
<date>Tuesday 27 April 2017</date>. We expect to arrive around
7.15pm. Approximately 12 people but I’ll confirm exact numbers closer to the day.

Regards,
Ivan

Write a REST service that:

  • Accepts a block of text
  • Extracts the relevant data
  • Calculate the GST and total excluding GST based on the extracted <total> (it includes GST)
  • Makes the extracted and calculated data available to the service’s client

Failure Conditions

The following failure conditions should be detected and made available to the client:

  • Opening tags that have no corresponding closing tag. In this case the whole message should be rejected.
  • Missing <total>. In this case the whole message should be rejected.
  • Missing <cost_centre>. In this case the ‘cost centre’ field in the output should be defaulted to ‘UNKNOWN’.