Atrium: sequenceAssertions for the new infix API

[robstoll]

Platform (jvm, js, android): jvm
Extension (none, kotlin 1.3, jdk8): none

Code related feature

We want to migrate the api-cc-infix-en_GB... modules which are based on Assert to Expect. We have already created the corresponding
modules api-infix-en_GB.... Also there are already fluent-en_GB... modules where we have already done the transition from Assert to Expect

Following the things you need to do:

• copy the file sequenceAssertions.kt from atrium-api-fluent-en_GB-common to atrium-api-infix-en_GB-common
  
  
  
  • adjust the signatures of the assertion functions so that they are infix functions (see sequenceAssertions.kt in atrium-api-cc-infix-en_GB-common for a guideline)
  
  
• copy the SequenceFeatureAssertionsSpec.kt from atrium-api-fluent-en_GB-common to atrium-api-infix-en_GB-common
  
  
  
  • introduce a function in the companion object for each assertion function so that we see the infix API in action (see SequenceFeatureAssertionsSpec in atrium-api-cc-infix-en_GB-jvm but use fun1, fun2 etc. to retrieve the name of the function instead of KFunction<...> -- use fun1<..>(...).name)
  
  

Your first contribution?

• Write a comment I'll work on this if you would like to take this issue over.
  This way we get the chance to revise the description in case things have changed in the meantime,
  we might give you additional hints and we can assign the task to you, so that others do not start as well.
• See Your first code contribution for guidelines.
• Do not hesitate to ask questions here or to contact us via Atrium's slack channel if you need help
  (Invite yourself in case you do not have an account yet).

[Caps-Looking]

I'd like to work on this.

[robstoll]

@Caps-Looking do you need help? Un-assigning so that others can take over

[ivanmiklec]

I'd like to work on this.

[robstoll]

Implemented with f42e2c4