skills.rest
finos
finosOFFICIAL
Explore all skills by this author →
WebsiteGitHub

build-service-behavioural-test-analysis

Analyze FINOS Common Cloud Controls service catalogs to plan Gherkin behavioural test coverage.

85|80|Updated Jul 26, 2023
Search Tags:#test planning#gherkin#compliance automation#ccc#behavioural testing#cloud api design#control catalog
One-click install
npx skills add https://github.com/finos/common-cloud-controls --skill build-service-behavioural-test-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-service-behavioural-test-analysis
Source: https://github.com/finos/common-cloud-controls/tree/main/skills/build-service-behavioural-test-analysis
Command: npx skills add https://github.com/finos/common-cloud-controls --skill build-service-behavioural-test-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of planning behavioural test coverage for FINOS Common Cloud Controls service catalogs, which requires mapping dozens of assessment requirements to testable scenarios, avoiding duplicate work from existing generic test steps, and designing minimal cloud API interfaces for test implementation.

Core Features & Use Cases

  • Catalog Ingestion & AR Classification: Automatically extracts assessment requirements from CCC controls.yaml and metadata.yaml files, classifies each as behavioural, not testable, or reusable from generic shared scenarios.
  • Test Planning & Reuse: Identifies existing generic test scenarios that can be tagged for the new service, and plans new feature files only for service-specific requirements that cannot be covered by shared steps.
  • Interface & Implementation Design: Produces a minimal cloud API interface design, cross-cloud implementation matrix for AWS/Azure/GCP, and plans for terraform fixtures, privateer configuration, and integration test coverage.
  • Use Case: A developer building Compliant Financial Infrastructure (CFI) test automation for a new cloud service (e.g. secrets management) can use this Skill to produce a complete analysis document in minutes, rather than manually reviewing the entire control catalog and designing test infrastructure from scratch.

Quick Start

Use the build-service-behavioural-test-analysis skill to analyze the catalogs/compute/virtual-machines/controls.yaml file and generate a behavioural test analysis document for the virtual-machines service.

Frequently Asked Questions about build-service-behavioural-test-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map FINOS Common Cloud Controls assessment requirements to Gherkin test scenarios?▼

You can map Common Cloud Controls assessment requirements to Gherkin scenarios by ingesting the service catalog's controls.yaml file, classifying each requirement as behavioural, reusable, or not testable, and generating new feature files only for service-specific requirements.

Can I reuse existing generic test steps when planning behavioural tests for a new cloud service catalog?▼

Yes, you can reuse existing generic test steps by identifying shared scenarios that already cover certain assessment requirements, tagging them for the new service, and planning new feature files only for requirements that cannot be covered by shared steps.

What is the best way to design a minimal cloud API interface for Compliant Financial Infrastructure test automation?▼

Designing a minimal cloud API interface for Compliant Financial Infrastructure involves analyzing the service control catalog to define service-specific API methods, producing a cross-cloud implementation matrix for AWS, Azure, and GCP, and planning terraform fixtures for test coverage.

Does the behavioural test analysis process generate physical implementation artifacts like terraform fixtures?▼

No, the behavioural test analysis process does not generate physical implementation artifacts; it produces structured analysis documents that plan terraform fixtures, privateer configuration, and integration test coverage without writing the actual code.

How do I classify cloud compliance controls by testability before writing feature files?▼

Classify cloud compliance controls by testability by extracting assessment requirements from the catalog metadata, then categorizing each control as behavioural, not testable, or reusable from generic shared scenarios to avoid duplicate test work.

Why should I use automated analysis for CCC service control catalogs instead of manual review?▼

Automated analysis eliminates the manual, error-prone work of reviewing entire control catalogs, automatically mapping assessment requirements to testable scenarios, and designing minimal cloud API interfaces, reducing a process that takes hours into minutes.

Related Skills

Explore More Software Engineering Skills→
finosfinos
85

build-threat-catalog

Generate schema-validated threat catalogs for FINOS Common Cloud Controls.

Official
Advanced
finosfinos
85

build-features-and-cloud-api

Transform approved cloud analysis documents into executable behavioral test stacks for AWS, Azure, and GCP deployments.

Official
Advanced
Azeem-2Azeem-2

cloud-native

Deploy and manage cloud-native infrastructure across multiple providers with IaC and GitOps.

Community
Advanced
Z1-TestZ1-Test

gherkin-authoring

Create executable behavior specifications using Gherkin Given/When/Then syntax.

Official
Intermediate