Automate Behavior-driven Development (Stanford WebCamp 2022)

Copyright © 2022 DOCOMO Innovations, Inc. All Rights Reserved. 1
Stanford WebCamp 2022
Automate Behavior-driven Development
Yas Naoi
Chief Architect, Cloud
DOCOMO Innovatins, Inc.

Yas
2
Copyright © 2022 DOCOMO Innovations, Inc. All Rights Reserved.
@yas
linkedin.com/in/yasnaoi

Yas
3
• Chief Architect, Cloud

Yas
4
• DOCOMO Innovations, Inc. (Palo Alto, CA)
• NTT DOCOMO Inc.

Yas
• DOCOMO Innovations, Inc. (Palo Alto, CA)
• NTT DOCOMO Inc.
• Cloud, DevOps, Agile Software Development
• d.o: 17 years
5

Our Team

/ Cloud Team Members /

CA
Yas
Baldwin
Kumiko
Tatsuya
Hiroki
Tamaki

India
Sachin
CA
Yas
Baldwin
Kumiko
Tatsuya
Hiroki
Tamaki

Japan
Xiaohua
Takumaru
Masami
Ryo
Tomohiro
India
Sachin
CA
Yas
Baldwin
Kumiko
Tatsuya
Hiroki
Tamaki Shota
Makoto

11
Cloud Orchestrator
Search: drupal cloud orchestrator

12
Cloud Orchestrator
Search: drupal cloud orchestrator

Multi-cloud Support
──────────────
13
Cloud Orchestrator

Multi-cloud Support
──────────────
§ AWS
14
Cloud Orchestrator

Multi-cloud Support
──────────────
§ AWS
§ Kubernetes
15
Cloud Orchestrator

Multi-cloud Support
──────────────
§ AWS
§ Kubernetes
§ OpenStack
16
Cloud Orchestrator

Multi-cloud Support
──────────────
§ AWS
§ Kubernetes
§ OpenStack
§ VMware
17
Cloud Orchestrator

Multi-cloud Support
──────────────
§ AWS
§ Kubernetes
§ OpenStack
§ VMware
§ Terraform Cloud
18
Cloud Orchestrator

Agenda
19

Agenda
• Development Model
• What’s Behat for Behavior-driven Development (BDD)
• Templating for Behat Test Scenarios
• Automated Testing for BDD
20

Software Development Lifecycle

Coding
Integration Testing
Component Design
Function Design Unit Testing
System Requirements System Testing
Business Requirements Acceptance Testing
V-model [Boehm 79]

Business Requirements
V-model [Boehm 79]

System Requirements
V-model [Boehm 79]

Component Design
System Requirements
V-model [Boehm 79]

Component Design
Function Design
System Requirements
V-model [Boehm 79]

Coding
Component Design
Function Design
System Requirements
V-model [Boehm 79]

Coding
Component Design
System Requirements
V-model [Boehm 79]

Coding
Integration Testing
Component Design
System Requirements
V-model [Boehm 79]

Coding
Integration Testing
Component Design
V-model [Boehm 79]

Coding
Integration Testing
Component Design
TDD
V-model [Boehm 79]

Coding
Integration Testing
Component Design
TDD
BDD
V-model [Boehm 79]

Coding
Integration Testing
Component Design
TDD
BDD
ATDD
V-model [Boehm 79]

Coding
Integration Testing
Component Design
V-model [Boehm 79]
✔TDD
BDD
ATDD
PHPUnit (Drupal)

Coding
Integration Testing
Component Design
V-model [Boehm 79]
✔TDD
✔BDD (ATDD)
PHPUnit (Drupal)
Behat+
Drupal
Extension

Behavior-driven Development
39

PHPUnit
/**
* Tests CRUD for K8s node.
*
* @throws Exception
*/
public function testNode(): void {
$cloud_context = $this->cloudContext;
$data = $this->createNodeTestFormData(self::K8S_NODE_REPEAT_COUNT);
$this->updateNodesMockData($data);
// Update k8s nodes.
$this->drupalGet("/clouds/k8s/$cloud_context/node/update");
$this->assertNoErrorMessage();
for ($i = 0; $i < self::K8S_NODE_REPEAT_COUNT; $i++) {
$this->assertSession()->pageTextContains($data[$i]['name']);
}
for ($i = 0, $num = 1; $i < self::K8S_NODE_REPEAT_COUNT; $i++, $num++) {
// Make sure the all node listing exists.
$this->drupalGet('/clouds/k8s/node');
$this->assertNoErrorMessage();
for ($j = 0; $j < $num; $j++) {
$this->assertSession()->pageTextContains($data[$j]['name']);
}
}
}

BDD Test Scenario Example by Behat
Feature: Login, Check the Clean State, and Logout
In order to list resources on the clean state
As a user
I need to have both Drupal and AWS IAM permissions
Scenario: Log in as "Anonymous user"
Given I am not logged in
When I visit "/clouds"
Then I should be on "/user/login"
And I should see the heading "Log in"
Scenario Outline: Access cloud service providers
Given I am logged in as a user with the <role> role
And I should not see the link "All" in the "nav_bar"
And I should <verb> "Add cloud service provider" in the "nav_bar"
When I go to "/clouds"
Then I should be on "/admin/structure/cloud_config/add"
And I should get a <code> HTTP response
And I should see the heading <heading>
Examples:
| role | verb | code | heading |
| "Authenticated user" | not see | 403 | "Access denied" |
| "Cloud administrator" | see | 200 | "Add cloud service provider" |
| "Administrator" | see | 200 | "Add cloud service provider" |

Behat + drupal-extension + Chrome Driver
2022 DOCOMO Innovations, Inc. All Rights Reserved. Confidential.
43
Application under Test
(AUT)
Test Framework

44
Test Framework

Test Framework
Features
in Gherkin
45

Test Framework
Features
in Gherkin
Drupal Ext.
Drush Ext.
API Driver
46

Test Framework
Features
in Gherkin
Drupal Ext.
Drush Ext.
API Driver
Mink Ext.
Chrome Ext.
WebDriver
47

Chrome
Driver
Test Framework
Features
in Gherkin
Drupal Ext.
Drush Ext.
API Driver
Mink Ext.
Chrome Ext.
WebDriver
WebDriver
Implementation
48

Chrome
Driver
Headless
Browser
Test Framework
Features
in Gherkin
Drupal Ext.
Drush Ext.
API Driver
Mink Ext.
Chrome Ext.
WebDriver
WebDriver
Implementation
<< Native API >>
49

Application under Test
(AUT)
Chrome
Driver
Headless
Browser
<< Native API >> << HTTP >>
Test Framework
Features
in Gherkin
Drupal Ext.
Drush Ext.
API Driver
Mink Ext.
Chrome Ext.
WebDriver
WebDriver
Implementation
50

Behat (Gherkin)
As a user
Examples:

Behat (Gherkin)
As a user
Examples:
Initial State / Condition

Behat (Gherkin)
As a user
Examples:
Action Take Place

Behat (Gherkin)
As a user
Examples:
Expected Result

I want to use parameters in scenarios!
As a user
Examples:

As a user
Examples:

How it works by natural language?
72

The Tricks
/**
* Log in as the existing user
*
* @Given I am logged in as user :name
*/
public function iAmLoggedInAsUser($name): void {
$user = user_load_by_name($name);
$this->getSession()->visit(user_pass_reset_url($user) . '/login');
}

The Tricks
/**
*
*/
}
Sentence

The Tricks
/**
*
*/
}
Parameter
Variable

The Tricks
/**
* Check if the current page contains no messages of the specified selector.
*
* @Then /^I should see no (?P<selector>(?:success|error|warning)) message$/
*/
public function assertSelectorNotVisible($selector): void {
switch ($selector) {
case 'success':
$selector_id = 'success_message_selector';
break;
case 'error':
$selector_id = 'error_message_selector';
break;
case 'warning':
$selector_id = 'warning_message_selector';
break;
default:
throw new ExpectationException(sprintf("Message type is invalid: %s",
$selector), $this->getSession()->getDriver());
}
$this->assertNotVisible($selector_id);
}
Regular
Expression

Predefined Scenario List: behat -dl
• Given I am an anonymous user
• Given I am not logged in
• Given I am logged in as a user with the :role role(s)
• Given I am logged in as a/an :role
• Given I am logged in as a user with the :role role(s) and I have the following fields:
• Given I am logged in as :name
• Given I am logged in as a user with the :permissions permission(s)
• Given I click :link in the :rowText row
• Given the cache has been cleared
• Given I run cron
• Given I am viewing a/an :type (content )with the title :title
• Given a/an :type (content )with the title :title
• Given I am viewing my :type (content )with the title :title
• Given :type content:
• Given I am viewing a/an :type( content):
• Given I am viewing a/an :vocabulary term with the name :name
• Given a/an :vocabulary term with the name :name
• Given users:
• Given :vocabulary terms:
• Given the/these (following )languages are available:
• Given I am logged in as user :name
• Given I am at :path
• Given for :field I enter :value
• Given I enter :value for :field
• Given I wait for AJAX to finish
• Given I press the :char key in the :field field
• Given I press :button in the :region( region)
• Given I fill in :value for :field in the :region( region)
• Given I fill in :field with :value in the :region( region)
• Given I check the box :checkbox
• Given I uncheck the box :checkbox
• Given /^(?:|I )am on (?:|the )homepage$/
• Given /^(?:|I )am on "(?P<page>[^"]+)"$/
• Given I should not see the error message( containing) :message
• Given I should not see the success message( containing) :message
• Given I should not see the warning message( containing) :message
• Given I run drush :command
• Given I run drush :command :arguments
• Given /^I wait for the batch job to finish$/
• Given there is an item in the system queue:
• When I wait :msec milliseconds
• When I check the box in the :rowText row
• When I fill in :value for :field in the row :row in the :region( region)
• When I follow/click :link in a row with :value set in :field in the :region( region)
• When I visit :path
• When I click :link
• When /^(?:|I )press "(?P<button>(?:[^"]|")*)"$/
• When I press the :button button
• When I follow/click :link in the :region( region)
• When I select the radio button :label with the id :id
• When I select the radio button :label
• When /^(?:|I )go to (?:|the )homepage$/
• When /^(?:|I )go to "(?P<page>[^"]+)"$/
• When /^(?:|I )reload the page$/
• When /^(?:|I )move backward one page$/
• When /^(?:|I )move forward one page$/
• When /^(?:|I )follow "(?P<link>(?:[^"]|")*)"$/
• When /^(?:|I )fill in "(?P<field>(?:[^"]|")*)" with "(?P<value>(?:[^"]|")*)"$/
• When /^(?:|I )fill in "(?P<field>(?:[^"]|")*)" with:$/
• When /^(?:|I )fill in "(?P<value>(?:[^"]|")*)" for "(?P<field>(?:[^"]|")*)"$/
• When /^(?:|I )fill in the following:$/
• When /^(?:|I )select "(?P<option>(?:[^"]|")*)" from "(?P<select>(?:[^"]|")*)"$/
• When /^(?:|I )additionally select "(?P<option>(?:[^"]|")*)" from "(?P<select>(?:[^"]|")*)"$/
• When /^(?:|I )check "(?P<option>(?:[^"]|")*)"$/
• When /^(?:|I )uncheck "(?P<option>(?:[^"]|")*)"$/
• When /^(?:|I )attach the file "(?P<path>[^"]*)" to "(?P<field>(?:[^"]|")*)"$/
• Then I log out
• Then I should see (the text ):text in the :rowText row
• Then I should not see (the text ):text in the :rowText row
• Then I (should )see the :link in the :rowText row
• Then I should be able to edit a/an :type( content)
• Then (I )break
• Then I should see (the text ):text1 or :text2 in the :rowText row
• Then I should see (the text ):text in the :rowText row in the :region( region)
• Then I take screenshot
• Then I should see the link :link
• Then I should not see the link :link
• Then I should not visibly see the link :link
• Then I (should )see the heading :heading
• Then I (should )not see the heading :heading
• Then I (should ) see the button :button
• Then I (should ) see the :button button
• Then I should not see the button :button
• Then I should not see the :button button
• Then I should see the heading :heading in the :region( region)
• Then I should see the :heading heading in the :region( region)
• Then I should see the link :link in the :region( region)
• Then I should not see the link :link in the :region( region)
• Then I should see( the text) :text in the :region( region)
• Then I should not see( the text) :text in the :region( region)
• Then I (should )see the text :text
• Then I should not see the text :text
• Then I should get a :code HTTP response
• Then I should not get a :code HTTP response
• Then /^(?:|I )should be on "(?P<page>[^"]+)"$/
• Then /^(?:|I )should be on (?:|the )homepage$/
• Then /^the (?i)url(?-i) should match (?P<pattern>"(?:[^"]|")*")$/
• Then /^the response status code should be (?P<code>d+)$/
• Then /^the response status code should not be (?P<code>d+)$/
• Then /^(?:|I )should see "(?P<text>(?:[^"]|")*)"$/
• Then /^(?:|I )should not see "(?P<text>(?:[^"]|")*)"$/
• Then /^(?:|I )should see text matching (?P<pattern>"(?:[^"]|")*")$/
• Then /^(?:|I )should not see text matching (?P<pattern>"(?:[^"]|")*")$/
• Then /^the response should contain "(?P<text>(?:[^"]|")*)"$/
• Then /^the response should not contain "(?P<text>(?:[^"]|")*)"$/
• Then /^(?:|I )should see "(?P<text>(?:[^"]|")*)" in the "(?P<element>[^"]*)" element$/
• Then /^(?:|I )should not see "(?P<text>(?:[^"]|")*)" in the "(?P<element>[^"]*)" element$/
• Then /^the "(?P<element>[^"]*)" element should contain "(?P<value>(?:[^"]|")*)"$/
• Then /^the "(?P<element>[^"]*)" element should not contain "(?P<value>(?:[^"]|")*)"$/
• Then /^(?:|I )should see an? "(?P<element>[^"]*)" element$/
• Then /^(?:|I )should not see an? "(?P<element>[^"]*)" element$/
• Then /^the "(?P<field>(?:[^"]|")*)" field should contain "(?P<value>(?:[^"]|")*)"$/
• Then /^the "(?P<field>(?:[^"]|")*)" field should not contain "(?P<value>(?:[^"]|")*)"$/
• Then /^(?:|I )should see (?P<num>d+) "(?P<element>[^"]*)" elements?$/
• Then /^the "(?P<checkbox>(?:[^"]|")*)" checkbox should be checked$/
• Then /^the "(?P<checkbox>(?:[^"]|")*)" checkbox is checked$/
• Then /^the checkbox "(?P<checkbox>(?:[^"]|")*)" (?:is|should be) checked$/
• Then /^the "(?P<checkbox>(?:[^"]|")*)" checkbox should (?:be unchecked|not be checked)$/
• Then /^the "(?P<checkbox>(?:[^"]|")*)" checkbox is (?:unchecked|not checked)$/
• Then /^the checkbox "(?P<checkbox>(?:[^"]|")*)" should (?:be unchecked|not be checked)$/
• Then /^the checkbox "(?P<checkbox>(?:[^"]|")*)" is (?:unchecked|not checked)$/
• Then /^print current URL$/
• Then /^print last response$/
• Then /^show last response$/
• Then I should see the error message( containing) :message
• Then I should see the following error message(s):
• Then I should not see the following error messages:
• Then I should see the success message( containing) :message
• Then I should see the following success messages:
• Then I should not see the following success messages:
• Then I should see the warning message( containing) :message
• Then I should see the following warning messages:
• Then I should not see the following warning messages:
• Then I should see the message( containing) :message
• Then I should not see the message( containing) :message
• Then /^I should see no (?P<selector>(?:success|error|warning)) message$/
• Then I should see neither error nor warning messages
• Then drush output should contain :output
• Then drush output should match :regex
• Then drush output should not contain :output
• Then print last drush output
• Then I should see the button :button in the :region( region)
• Then I should see the :button button in the :region( region)
• Then I should not see the button :button in the :region( region)
• Then I should not see the :button button in the :region( region)
• Then I( should) see the :tag element in the :region( region)
• Then I( should) not see the :tag element in the :region( region)
• Then I( should) not see :text in the :tag element in the :region( region)
• Then I( should) see the :tag element with the :attribute attribute set to :value in the :region( region)
• Then I( should) see :text in the :tag element with the :attribute attribute set to :value in the :region( region)
• Then I( should) see :text in the :tag element with the :property CSS property set to :value in the :region( region)

But scenario outline is not enough!
78

I want to use parameters for everything!
Scenario Outline: Launch an EC2 instance
Given I am logged in as user "{{ user_name }}"
When I visit "/clouds/design/server_template/"
And I click <instance_name>{{ cloud_context }}
And I click "Launch"
And the url should match "/launch"
And I check the box "Automatically terminate instance"
And I press "Launch"
Then I should be on "/clouds/aws_cloud/{{ cloud_context }}/instance"
And I should see "pending" in the <instance_name> row
And I should see <instance_type> in the <instance_name> row
And I should see "{{ availability_zone }}" in the <instance_name> row
Examples:
| instance_name | instance_type |
| "{{ instance_name_1 }}" | "{{ instance_type_1 }}" |

I want to use parameters for everything!
Scenario Outline: Launch an EC2 instance
Given I am logged in as user "{{ user_name }}"
When I visit "/clouds/design/server_template/"
And I click <instance_name>{{ cloud_context }}
And I click "Launch"
And the url should match "/launch"
And I check the box "Automatically terminate instance"
And I press "Launch"
Then I should be on "/clouds/aws_cloud/{{ cloud_context }}/instance"
And I should see "pending" in the <instance_name> row
And I should see <instance_type> in the <instance_name> row
And I should see "{{ availability_zone }}" in the <instance_name> row
Examples:
| instance_name | instance_type |
Twig Template!

Get Parameterized

Get Parameterized
docker build

Get Parameterized
docker build
RUN composer require
drupal/cloud
drupal/drupal-extension
...

Get Parameterized
Packagist:
drupal/cloud_orchestrator
incl. drupal/cloud
Feature: ...
Scenario Outline: ...
Examples:
docker build
drupal/cloud
...
<< Download >>

Get Parameterized
docker run docomoinnovations/cloud_orchestrator
Packagist:
incl. drupal/cloud
Feature: ...
Examples:
docker build
drupal/cloud
...
<< Download >>
<< docker run >>

Get Parameterized
Run drush cloud:behat:preprocess
• Read a YAML file whih contains parameter mappings
• Replace {{...}} as an input variable
Packagist:
incl. drupal/cloud
Feature: ...
Examples:
docker build
drupal/cloud
...
<< Download >>
<< docker run >>

Get Parameterized
private_params.yml
e.g.
This is a placeholder:
Cloud Orchestrator
Packagist:
incl. drupal/cloud
Feature: ...
Examples:
docker build
drupal/cloud
...
<< Read parameter files>>
<< Download >>
<< docker run >>

Get Parameterized
Feature: ...
...<This is a placeholder>...
Examples:
| This is a placeholder |
| {{This is a placeholder}} |
private_params.yml
e.g.
Cloud Orchestrator
Packagist:
incl. drupal/cloud
Feature: ...
Examples:
docker build
drupal/cloud
...
<< Read Feature template files>>
<< Download >>
<< docker run >>

Get Parameterized
Feature: ...
Examples:
private_params.yml
e.g.
Cloud Orchestrator
Feature: ...
Examples:
| Cloud Orchestrator |
Packagist:
incl. drupal/cloud
Feature: ...
Examples:
docker build
drupal/cloud
...
<< Output actual feature files>>
<< Download >>
<< docker run >>

Get Parameterized
Run behat command
run_behat.sh
Feature: ...
Examples:
private_params.yml
e.g.
Cloud Orchestrator
Feature: ...
Examples:
Packagist:
incl. drupal/cloud
Feature: ...
Examples:
docker build
drupal/cloud
...
<< Read feature files>>
<< Download >>
<< docker run >>

Get Parameterized
Run behat command
run_behat.sh
Feature: ...
Examples:
private_params.yml
e.g.
Cloud Orchestrator
Feature: ...
Examples:
Execute BDD tests
and get Output
Packagist:
incl. drupal/cloud
Feature: ...
Examples:
docker build
drupal/cloud
...
<< Process features >>
<< Read feature files>>
<< docker run >>
<< Download >>

We Test Our Code

We Want This One!

GitLab CI/CD Pipeline

GitLab CI/CD Pipeline Architecture Basics

Developer

Developer
GitLab Master

GitLab Master GitLab Runner
Developer

GitLab Master
GitLab
Repository
Developer
GitLab Runner

GitLab Master
CI/CD
Pipeline
GitLab
Repository
Developer
GitLab Runner

CI/CD
Pipeline
GitLab
Repository
Developer
gitlab-runner 1
gitlab-runner 2
…
gitlab-runner N

GitLab
Container
Registry
CI/CD
Pipeline
GitLab
Repository
Developer
gitlab-runner 1
gitlab-runner 2
…
gitlab-runner N

CI/CD
Pipeline
GitLab
Repository
Developer
GitLab
Container
Registry
gitlab-runner 1
gitlab-runner 2
…
gitlab-runner N

EC2
Our GitLab CI/CD Pipeline Architecture
GitLab Master (SaaS)
CI/CD
Pipeline
GitLab
Repository
Developer
Slack
GitLab
Container Registry
gitlab-runner 1
gitlab-runner 2
gitlab-runner 3
gitlab-runner 4

Slack Integration

How can we build CI/CD pipeline?
112

.gitlab-ci.yml
stages:
- run_tests
- .post
variables:
UPDATE: 20220408a
WEB_ROOT: '/var/www/html/web'
CLOUD_HOME: "${WEB_ROOT}/modules/contrib/cloud"
BROWSER_OUTPUT: "${WEB_ROOT}/sites/simpletest/browser_output/"
IMAGE_TAG: 9.4.x-arm64
.preprocess_template: &preprocess_definition
image:
name: "${CI_REGISTRY_IMAGE}:${IMAGE_TAG}"
stage: run_tests
only:
- branches
# - merge_requests
before_script: |
whoami
sudo service apache2 start
sudo service memcached start
sudo mkdir -p "${WEB_ROOT}/simpletest/${CI_PIPELINE_ID}"
sudo mount -t tmpfs -o size=8G tmpfs "${WEB_ROOT}/simpletest/${CI_PIPELINE_ID}"
sudo chmod 777 -R "${WEB_ROOT}/simpletest"
rm -rf "${CLOUD_HOME}" && cp -ar "${PWD}" "${CLOUD_HOME}”
.artifacts_template: &postprocess_definition
after_script: |
mkdir -p "${BROWSER_OUTPUT}"
if [ -d "${BROWSER_OUTPUT}" ]; then cp -ar "${BROWSER_OUTPUT}" "${CI_PROJECT_DIR}/";
else mkdir -p "${BROWSER_OUTPUT}" && touch "${BROWSER_OUTPUT}/NO_ARTIFACTS.txt"; fi
php -v
drush status
...

.gitlab-ci.yml
• Describe the pipeline definition in one YAML file
• Put root (top) directory of your branch
• Get started
– https://docs.gitlab.com/ee/ci/quick_start/

Demo
• Behat
• GitLab CI/CD Pipeline

Our Custom Extension to drupal-extension
1. Logged in as the existing user without password
– Using drush user:login
2. Take a screenshot, which is very useful in troubleshooting
– Not only with Selenium + @javascript, but Chrome Extension or w/o
@javascript
3. Specifying a region with the row index of a table
– Especially when the same labels are used in multiple rows
4. Assert only the success message shows
– Namely, neither error or warning messages show
117

118
– Not only with Selenium + @javascript, but Chrome Extension
or w/o @javascript annotation

119

120

121

Known Issues: Solutions
1. User login sometimes fails due to "Username" is not found
– Workaround: add a longer sleep after chromium started
2. The text in checkbox/link is visible, but not ready to be clicked
– Add 500 ms sleep before such action
3. Cannot distinguish DOM objects if the same text are set
– For the table rows
4. Cannot login with a role created in the same Behat process
– Workaround: divide a feature file to run Behat for each
– Avoid using login with such role
122

Where to Find Our Solutions
124
• Behat feature files & configurations
– https://git.drupalcode.org/project/cloud/-/tree/5.x/tests/src/Behat
– https://git.drupalcode.org/project/cloud/-/tree/5.x/modules/cloud_service_providers/aws_cloud/tests/src/Behat
– https://git.drupalcode.org/project/cloud/-/tree/5.x/modules/cloud_service_providers/k8s/tests/src/Behat
• Drupal extensions with our custom functions
– https://github.com/docomoinnovations/drupalextension

Resources
125
• Cloud Orchestrator
– https://drupal.org/project/cloud
– https://cloud.airgap.host
• YouTube Channel
– https://bit.ly/2TJssME

126
Thank you!
"Coming together is a beginning, keeping together is
a progress; working together is a success.“
- Henry Ford
@yas
linkedin.com/in/yasnaoi

Automate Behavior-driven Development (Stanford WebCamp 2022)

Recommended

Recommended

More Related Content

Similar to Automate Behavior-driven Development (Stanford WebCamp 2022)

Similar to Automate Behavior-driven Development (Stanford WebCamp 2022) (20)

More from DOCOMO Innovations, Inc.

More from DOCOMO Innovations, Inc. (10)

Recently uploaded

Recently uploaded (20)

Automate Behavior-driven Development (Stanford WebCamp 2022)