#e2e

So, I needed to re-use features and saw that #gherkin does not have feature
level examples.

I wonder why that is?

Anyway, my #e2e test runner now has support for that.

https://github.com/NordicSemiconductor/cloud-e2e-bdd-test-runner-js/commit/ef338277b2603925d3b3c5be7488912f69fc8a03#diff-ea306231f3e59f77089f33442f3eb6a87dfacec6c1550eb1be2a2ad492c62c37

I've added an #e2e test for ensuring that calls to an external API work, and I
really love that I can tie this all in one test file:

1. set up the expected call to the remote API
2. Describe the action that triggers this call
3. Verify that it happened

https://github.com/NordicSemiconductor/asset-tracker-cloud-aws-js/blob/676490a0ddc6d8489801c834412ce336846aa218/features/UnwiredLabsCellGeolocation.feature

This is a great example of why I like #BDD #e2e tests and how they support
refactoring: the only thing that changed (while refactoring the entire data
storage solution) was the query language part, the result, and tested scenarios
stayed the same.

Progress in the right direction: #e2e tests now running for
@bifravst on
@github actions against @azure.

I am still not able to test that setting up the entire solution works from a
blank account, but at least I can verify that updating an existing one does not
break it.

So, started to separate instances for #e2e testing of
@bifravst on #Azure
(https://bifravst.gitbook.io/bifravst/bifravst-on-azure-wip/continuousintegration)
and suddenly the azure functions cli stops publishing all functions, while
running them locally it lists them all. Time for the weekend I guess :/
@AzureSupport

#e2e test for @bifravst on
@Azure are getting somewhere ... however every day
brings new hurdles. Today I discovered that I can't programmatically
authenticate users against Azure AD B2C using the same function app, because it
can only have one Issuer Url configured for auth.

So this is fine for CI #e2e test, but you it means you can't easily run these
test against a development instance. :/

Also, the Issuer URL has a different value for developer generated tokens. Which
means a different config in prod vs. test. 🤕

Oh, why am I not surprise. I've started to look into #e2e testing the
@bifravst Azure flavour and I need to do even
more manual set-up on the portal to start using B2C authentication in the test
runner:
https://docs.microsoft.com/en-us/azure/active-directory-b2c/microsoft-graph-get-started?tabs=app-reg-ga
No fun building robust easy to change apps on
@Azure.

Today I started to work on #BDD #e2e tests for a cloud-native app, means I need
to test directly against the @awscloud SDK.

@cucumberbdd feature file:
https://github.com/bifravst/aws/blob/a42789d8fd79578a315feb54f7e1f3cc93eea412/features/IoTUserPolicy.feature

and this is the testrunner implementation:
https://github.com/coderbyheart/bdd-feature-runner-aws/blob/fef4f244bc0c278703a6c51f4e179e2d7c888543/src/steps/aws-sdk.ts

I had two super-interesting sessions on #javascript and #iot #e2e testing, so I
forgot to take sessions. My slides on the #e2e testing are here:
https://coderbyheart.com/it-does-not-run-on-my-machine/

I also mentioned this technique how I deploy lambdas to AWS:
https://coderbyheart.com/how-i-package-typescript-lambdas-for-aws/