bizz84 / acceptancemark Goto Github PK

This is an absolutely fantastic tool. I love it. Is support for generating Quick specs on the horizon?

Purpose: See test success/failures via a file report that can be stored as an artifact in CI.

As the AcceptanceMark test suite runs, we want to generate a test report.

One way of doing this is to extend the generated test methods to pipe the results (success/failure with details) into an HTML file with green/red tests similar to the Fitnesse Test Report.

One advantage of this is that if the test suite crashed, all test results up to that point will have been already written into a file. NOTE how to deal with tests running concurrently? Need to ensure the report file is written atomically and in order

The generated test methods are the ideal place for this as they have knowledge of the inputs, outputs and expected values for each test.

Purpose: Keep AcceptanceMark Test target up to date as input files are modified.

By running amtool, all the required test files are written into an output folder.

Unless amtool keeps the test target up to date, the user is responsible for making sure that all the test files are included in the test target, which is error prone and a time drain.

We need a way of hooking into the client Xcode project to keep the test target up to date.

And make tests index start from 1, not 0.

This is so that tests read like this:

func testMethod_run1()
func testMethod_run2()
...

rather than like this:

func testMethod_0()
func testMethod_1()
...

Test files should be named:

<namespace>_<heading>Tests.swift 

Currently, this is:

<namespace>_<heading>.swift 

Does the amtool require compatibility with Xcode 9. Would like to start using in a project using Swift 4 and Xcode 9.

Are there plans to make this be available for Swift 4?

Purpose: Make it easier to get amtool executable (ideally no manual compilation needed)

Currently, AcceptanceMark does not provide a way of describing what each test does.
It would be useful to add a description column to describe what the test will do. Example:

One way to do this is to add an additional optional column separator after the outputs. The additional description column could be used to name the test so that the generated method could change from this:

func testDateFormatting_row1()

to this:

func testDateFormatting_row1_formatsTheDateInEnglish()

Purpose: Write a command line tool to generate XCTests from a set of .md files encoding business rules.

See amtool Specification file for details.

TODO

• Add Xcode macOS Command Line Tool target to project, named amtool
• Parse --input-dir and -i command line argument to specify input directory for reading .md files
• For each .md file in input directory, run test generator component

This is a valid markdown table:

This isn't.

| input1 |input2|| output |
| --- | -------|| ------- |
| 1 | 2 || 3 |

It would be desirable to ensure all tables are rendered correctly, while preserving the same rules for input/output fields