bcf6bce793
* added basic detection for ambiguous steps, but causes an error and not yet recorded in the reports as 'Ambiguous', and no test cases figured out yet * added initial support for detection of ambiguous steps - further work take a look at how cuke jvm report ambiguous steps and sets the step status to 'ambiguous' rather than my current solution which just blows the test up as a regular step error * added suite_context_test and also introduced missing 'ambiguous' status to make cucumber jvm' * update CHANGELOG for ambiguous step defs * missed file from commit * added internal/formatters/fmt_multi_test.go * add tests for other peoples code * added "ambigous" to the help text * tests * added some more tests for attachments * Update internal/flags/flags.go Co-authored-by: Viacheslav Poturaev <nanopeni@gmail.com> --------- Co-authored-by: Viacheslav Poturaev <nanopeni@gmail.com>
28 строки
766 Б
Go
28 строки
766 Б
Go
package godog
|
|
|
|
import (
|
|
"context"
|
|
"testing"
|
|
|
|
"github.com/stretchr/testify/assert"
|
|
)
|
|
|
|
func TestAttach(t *testing.T) {
|
|
|
|
ctx := context.Background()
|
|
|
|
ctx = Attach(ctx, Attachment{Body: []byte("body1"), FileName: "fileName1", MediaType: "mediaType1"})
|
|
ctx = Attach(ctx, Attachment{Body: []byte("body2"), FileName: "fileName2", MediaType: "mediaType2"})
|
|
|
|
attachments := Attachments(ctx)
|
|
|
|
assert.Equal(t, 2, len(attachments))
|
|
|
|
assert.Equal(t, []byte("body1"), attachments[0].Body)
|
|
assert.Equal(t, "fileName1", attachments[0].FileName)
|
|
assert.Equal(t, "mediaType1", attachments[0].MediaType)
|
|
|
|
assert.Equal(t, []byte("body2"), attachments[1].Body)
|
|
assert.Equal(t, "fileName2", attachments[1].FileName)
|
|
assert.Equal(t, "mediaType2", attachments[1].MediaType)
|
|
}
|