Check if a command is available on the system

Parse template and extract all undefined variables. This helps identify what variables need to be provided.

Get test configuration with optional overrides

Load and parse a YAML file

Mock base64 decoding

Mock base64 encoding

Mock the bool filter

Mock the bool filter

Mock the lookup function

Mock the to_uuid filter

Mock the to_uuid filter

Mock the version comparison filter

Set up test fixtures.

Set up test fixtures.

Clean up patches.

Ensure algo_* variables produce booleans in their fallback cases.

Test that all when: conditions in the codebase would work with boolean types.

Test that alternative ingress IP uses SNAT instead of MASQUERADE.

Test that our fixes work with Ansible 12's strict type checking. This simulates what Ansible 12 will do with our variables.

Check that main playbook has valid syntax

Test AWS EC2 instance type naming

Test that keys are in valid base64 format

Test that the bool filter correctly converts string values.

Test NAT rules when both VPN types are enabled.

Test CA certificate - uses real certs if available, else validates config (Issue #75, #153)

Test CA password validation and handling

Test certificate chain - uses real certs if available, else validates config

Test client certificates - uses real certs if available, else validates config (Issue #75, #153)

Check that cloud-init header is exactly '#cloud-config' without space

Check that when: conditions using these variables will work with booleans.

Check that config.cfg is valid YAML

Test that critical templates render with test data

Test DigitalOcean droplet size naming

Test dnsmasq configuration syntax

Test that DNS access is restricted to VPN clients only.

Test that the Algo Docker image can be built

Check that Dockerfile exists and is not empty

Test handling of duplicate usernames

Test various edge cases for inline comment detection. Ensures we correctly handle hashes in strings, escaped hashes, and various comment patt

Test that get_aws_connection_info is called without boto3 parameter.

Test Hetzner server type configurations (issue #14730)

Verify algo_* variables in input.yml don't produce string 'false'.

Test IP address and CIDR notation validation

Test that IPsec FORWARD rules still use policy matching (this is correct).

Test that IPsec traffic gets proper NAT rules without policy matching.

Test iptables rules syntax

Verify ipv6_support in facts.yml doesn't produce string 'true'/'false'.

Ensure ipv6_support produces boolean, not string 'true'/'false'.

Test that the same private key always produces the same public key

Test that lightsail_region_facts can be imported.

Test that localhost deployment requirements are met

Test that mobile config files would be valid XML

Test the mobileconfig template with various scenarios.

Check for bare 'false' after else in Jinja expressions.

Scan for any remaining bare 'true'/'false' in Jinja2 expressions.

Verify that boto3 parameter is not present in the source code.

Look for patterns that would cause Ansible 12 boolean type issues in Algo code.

Scan all YAML files for set_fact with string 'true'/'false'.

Specifically test the OpenSSL file that had the original bug.

Test the OpenSSL task template that had the inline comment issue.

Test that output interface is specified in NAT rules.

Test that the correct number of packages are included.

Test PKCS#12 files - uses real files if available, else validates config (Issue #14755, #14718)

Test that configured ports are in valid ranges

Test that package pre-installation is disabled by default.

Test that package pre-installation is disabled when set to false.

Test that package pre-installation works when enabled.

Check that pyproject.toml exists and has dependencies

Ensure we're running on Python 3.11+

Regression test for issue #14822. Ensures that the deprecated boto3 parameter is not used.

Regression test: ensure we never produce string literals 'true' or 'false'. This is what breaks Ansible 12.0.0.

Regression test for the specific OpenSSL inline comment bug that was reported. Tests that we correctly detect inline comments in the exact pa

Test that config.cfg has valid Scaleway settings

Test that main.yml uses 'project' instead of deprecated 'organization' parameter

Test that the role correctly uses Scaleway Marketplace API

Test that prompts.yml collects organization/project ID from user

Test server certificates - uses real certs if available, else validates config

Test server selection string parsing (issue #14727)

Run shellcheck on shell scripts

Test SSH tunnel configuration syntax

Test that SSH keys aren't regenerated unnecessarily

Test that StrongSwan configs can be validated

Test StrongSwan ipsec.conf syntax

Test all StrongSwan templates with various configurations.

Test templates with different conditional states

Check Jinja2 template files for boolean usage.

Test that all templates have valid Jinja2 syntax

Test that template files handle boolean variables correctly.

Test that user configs would be generated correctly

Test that user lists in config.cfg are parsed correctly