Skip to content

test: synchronizing gherkin spec #1723

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 13, 2023
Merged

test: synchronizing gherkin spec #1723

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
70 changes: 70 additions & 0 deletions tests/bdd/features/azure_functions_metadata.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
Feature: Extracting Metadata for Azure Function Apps

Background:
Given an agent configured with
| setting | value |
| cloud_provider | azure |

Scenario Outline: Azure Function App with minimum set of environment variables present in expected format
Given the following environment variables are present
| name | value |
| FUNCTIONS_EXTENSION_VERSION | version |
| WEBSITE_OWNER_NAME | d2cd53b3-acdc-4964-9563-3f5201556a81+faas_group-CentralUSwebspace-Linux |
| WEBSITE_SITE_NAME | site_name |
When cloud metadata is collected
Then cloud metadata is not null
And cloud metadata 'account.id' is 'd2cd53b3-acdc-4964-9563-3f5201556a81'
And cloud metadata 'provider' is 'azure'
And cloud metadata 'service.name' is 'functions'
And cloud metadata 'instance.name' is 'site_name'
And cloud metadata 'project.name' is 'faas_group'
And cloud metadata 'region' is 'CentralUS'

Scenario Outline: Azure Function App with typical set of environment variables present in expected format
Given the following environment variables are present
| name | value |
| FUNCTIONS_EXTENSION_VERSION | version |
| WEBSITE_OWNER_NAME | d2cd53b3-acdc-4964-9563-3f5201556a81+faas_group-CentralUSwebspace-Linux |
| WEBSITE_SITE_NAME | site_name |
| REGION_NAME | Central US |
| WEBSITE_RESOURCE_GROUP | faas_group_from_env |
When cloud metadata is collected
Then cloud metadata is not null
And cloud metadata 'account.id' is 'd2cd53b3-acdc-4964-9563-3f5201556a81'
And cloud metadata 'provider' is 'azure'
And cloud metadata 'service.name' is 'functions'
And cloud metadata 'instance.name' is 'site_name'
And cloud metadata 'project.name' is 'faas_group_from_env'
And cloud metadata 'region' is 'Central US'

Scenario: WEBSITE_OWNER_NAME environment variable not expected format
Given the following environment variables are present
| name | value |
| WEBSITE_OWNER_NAME | d2cd53b3-acdc-4964-9563-3f5201556a81-faas_group-CentralUSwebspace-Linux |
| WEBSITE_SITE_NAME | site_name |
When cloud metadata is collected
Then cloud metadata is null

Scenario: Missing FUNCTIONS_EXTENSION_VERSION environment variable
Given the following environment variables are present
| name | value |
| WEBSITE_OWNER_NAME | d2cd53b3-acdc-4964-9563-3f5201556a81+faas_group-CentralUSwebspace-Linux |
| WEBSITE_SITE_NAME | site_name |
When cloud metadata is collected
Then cloud metadata is null

Scenario: Missing WEBSITE_OWNER_NAME environment variable
Given the following environment variables are present
| name | value |
| FUNCTIONS_EXTENSION_VERSION | version |
| WEBSITE_SITE_NAME | site_name |
When cloud metadata is collected
Then cloud metadata is null

Scenario: Missing WEBSITE_SITE_NAME environment variable
Given the following environment variables are present
| name | value |
| FUNCTIONS_EXTENSION_VERSION | version |
| WEBSITE_OWNER_NAME | d2cd53b3-acdc-4964-9563-3f5201556a81+faas_group-CentralUSwebspace-Linux |
When cloud metadata is collected
Then cloud metadata is null