vinceburn/doubleagent

Mock Server Written in Swift

doubleagent's Issues

toDoubleAgent: Support macOS Alias for Mapping File

Give more flexibility on use case sharing by allowing macOS filas alias to be use for the mapping file

To Double Agent Tool

Add a terminal app that can process a folder of input file and send them to a running Double Agent.

Validate Docker

1. Validate that the Vapor template docker files are working properly.
2. Add Docker instruction to the README file

toDoubleAgent: Simplify Development Setup

Current Development setup requires user to do some manual configuration and generate an Xcode project from the swift package manager.
Then they need to setup a custom working directory in the scheme.

AC

• Commit an Xcode project setup with a working directory in within the repository. (use $(SRCROOT) to point to the folder)
• Add example files to custom working directory that can be use while developing.
• Add no-upload flag in the scheme arguments.

Documentation: Repo Structure

Document the Repo Structure in the README

toDoubleAgent: Creation Error Message

When the toDoubleAgent app upload the files to the mock server it prints out the request status code in the form "Response: 400".

Would be nice to update that message so it standout when the response is not a 200.

Maybe: "❌ Response: 400"

toDoubleAgent: Add command line argument validation

Currently when a non existing command line argument is use (e.g. --Map instead of --map) the toDoubleAgent tool act as if the argument was not present. Which is reasonable, but the user will believe that the commend worked as he expected.

Solution: Report an error when an invalid argument is used, it is most likely an error the user would like to know about to avoid lost of time debugging.

Call Mapping on Body

Some POST API differ only by their body information. Add functionality to have different response for different body.

Server API: Get All

The get all API currently returns both part of all call (call matching info and response data), which can make the response very big and slow.

Remove the response data from the response.

Slow Response Time

Especially when running the server from Docker the response time is slower than expected.

Currently it is not that bad as it allow to fully appreciate the loading visual of a screen, so priority to fix will not be high.

Might relate to #8

resetAll API: Slow

Large data set will cause resetAll to take longer than expected.
ex. 16 call with 3/4 of the input files being over 300k and 2 being around 800k

Check to improve record removal from the data base.

Improve Multiple Match Error

Improve the multiple match error to include useful information to help identify what is the problem with the used data set

Lookup Body: More Flexibility

Currently the lookup body must be a String. It can be a String representing a JSON, but it must be a string, which leads to a lot of escaping.

Make it in a way that it could be passes as a String or as a JSON Object, like for the response.body.

Note

The current use of a String is due to some equality problem when using the Codability.AnyCodable wrapper to store the information.

On Successful Match add more info to header

Currently when the mock server find a matching call, a header is added to the response to indicate the ID of the call info that was returned.

Would it be interesting to add, path, method and lookup info to the returned headers?

toDoubleAgent: Better documentation

Complete the toDoubleAgent documentation

README: Document the Mock Server API

Double Agent use an API to update / change its mapping while running. Document it in the README file.

toDoubleAgent: Unit Tests

Rewrite the toDoubleAgent tool using TDD for fun

toDoubleAgent: Resolve macOS Alias file for .json

Different Mock Use Case can use a shared common data set.

To avoid duplicating the files in every data set macOS Alias could be use.

Currently Alias are not supported.

AC

• Add support for Alias of .json file (alias must keep the .json extension to be part of the file to be resolved)
• The original files are copied in the __processed folder
• The original files are not modified by the map processing

Dev Note

URL(resolvingAliasFileAt: $0)

Help API: Document the Mock Server API

Double Agent use an API to update / change its mapping while running. Document it in the Help API.

DB: Revisit DB Scheme

The response part of the Call Info doesn't need to be searchable, would it be better to use "group" instead?

toDoubleAgent: Help Comment have side effect

Currently the toDoubleAgent --help command will create and modify the __precessed folder.

The help command should have no side effects.