cambios profundos con grok

This commit is contained in:
2026-05-26 00:42:42 +02:00
parent ee8cfa03ea
commit 19ea13dadd
99 changed files with 1447 additions and 2597 deletions
@@ -0,0 +1,51 @@
# Updated via Autotest Editor - 2026-05-25T21:52:12.010Z
# Source of truth: this YAML file
id: core-virtualization-check-snapshot_backup_restore_and_consistency
module: core
group: core-virtualization
title: Verify VM snapshot and restore operations maintain full system consistency
description: Verify VM snapshot and restore operations maintain full system consistency
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Hypervisor Access
value: vCenter, Hyper-V Manager, Proxmox, or virsh (SSH/API)
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: partial
file: tests/core/virtualization.spec.ts
custom_fields:
original_action: check
partialNotes: >-
Post-restore consistency checks via admin portal automated; snapshot/restore operation needs
hypervisor access
automatable:
- Portal UI configuration and verification steps (already partially automated)
- Data extraction and reporting of current settings
notYet:
- >-
Post-restore consistency checks via admin portal automated; snapshot/restore operation needs
hypervisor access
- Hypervisor-level operations (vCenter, libvirt, vSphere) not reachable from browser automation
- Long-running load or HA failover scenarios need dedicated lab infrastructure
@@ -0,0 +1,46 @@
# Updated via Autotest Editor - 2026-05-25T21:52:12.011Z
# Source of truth: this YAML file
id: core-virtualization-write-guest_agent_integration
module: core
group: core-virtualization
title: Record guest agent integration status for each supported hypervisor
description: Record guest agent integration status for each supported hypervisor
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Hypervisor Access
value: vCenter, Hyper-V Manager, Proxmox, or virsh (SSH/API)
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: manual
file: tests/core/virtualization.spec.ts
custom_fields:
original_action: write
manualReason: Requires direct access to hypervisor console (vCenter, Hyper-V Manager, virsh)
automatable:
- Most UI-driven configuration and verification steps via Playwright
notYet:
- Requires direct access to hypervisor console (vCenter, Hyper-V Manager, virsh)
- Hypervisor-level operations (vCenter, libvirt, vSphere) not reachable from browser automation
- Long-running load or HA failover scenarios need dedicated lab infrastructure
@@ -0,0 +1,46 @@
# Updated via Autotest Editor - 2026-05-25T21:52:12.012Z
# Source of truth: this YAML file
id: core-virtualization-write-resource_allocation_vcpu_vram_vdisk
module: core
group: core-virtualization
title: Record vCPU, vRAM, and vDisk resource allocation for deployment templates
description: Record vCPU, vRAM, and vDisk resource allocation for deployment templates
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Hypervisor Access
value: vCenter, Hyper-V Manager, Proxmox, or virsh (SSH/API)
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: manual
file: tests/core/virtualization.spec.ts
custom_fields:
original_action: write
manualReason: Hypervisor management plane access required; not exposed in PBX admin portal
automatable:
- Most UI-driven configuration and verification steps via Playwright
notYet:
- Hypervisor management plane access required; not exposed in PBX admin portal
- Hypervisor-level operations (vCenter, libvirt, vSphere) not reachable from browser automation
- Long-running load or HA failover scenarios need dedicated lab infrastructure
@@ -0,0 +1,46 @@
# Updated via Autotest Editor - 2026-05-25T21:52:12.013Z
# Source of truth: this YAML file
id: core-virtualization-write-storage_thin_vs_thick_provisioning
module: core
group: core-virtualization
title: Record storage provisioning type and performance implications for each hypervisor
description: Record storage provisioning type and performance implications for each hypervisor
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Hypervisor Access
value: vCenter, Hyper-V Manager, Proxmox, or virsh (SSH/API)
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: manual
file: tests/core/virtualization.spec.ts
custom_fields:
original_action: write
manualReason: Storage details only visible in hypervisor storage management interface
automatable:
- Most UI-driven configuration and verification steps via Playwright
notYet:
- Storage details only visible in hypervisor storage management interface
- Hypervisor-level operations (vCenter, libvirt, vSphere) not reachable from browser automation
- Long-running load or HA failover scenarios need dedicated lab infrastructure
@@ -0,0 +1,45 @@
# Updated via Autotest Editor - 2026-05-25T21:52:12.014Z
# Source of truth: this YAML file
id: core-virtualization-write-supported_hypervisors_deployment
module: core
group: core-virtualization
title: Record the list of supported hypervisors and deployment methods from the download portal
description: Record the list of supported hypervisors and deployment methods from the download portal
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Hypervisor Access
value: vCenter, Hyper-V Manager, Proxmox, or virsh (SSH/API)
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: automated
file: tests/core/virtualization.spec.ts
custom_fields:
original_action: write
automatable:
- Full end-to-end execution via Playwright against the admin portal UI
- Navigation, form interaction, and assertions are scriptable
notYet:
- Hypervisor-level operations (vCenter, libvirt, vSphere) not reachable from browser automation
- Long-running load or HA failover scenarios need dedicated lab infrastructure
@@ -0,0 +1,46 @@
# Updated via Autotest Editor - 2026-05-25T21:52:12.015Z
# Source of truth: this YAML file
id: core-virtualization-write-virtual_networking_configuration
module: core
group: core-virtualization
title: 'Record virtual networking configuration: virtual switches, VLANs, NIC assignments'
description: 'Record virtual networking configuration: virtual switches, VLANs, NIC assignments'
priority: Medium
tags: []
references: []
dependencies:
- label: Admin Portal
value: https://pbx.local:4443 (configure via $BASE_URL)
- label: Repository URL
value: ${BASE_URL}/downloads or $REPO_URL
- label: Protocol
value: HTTPS (admin portal) + optional SSH/CLI
- label: Hypervisor Access
value: vCenter, Hyper-V Manager, Proxmox, or virsh (SSH/API)
- label: Credentials
value: Admin user with sufficient privileges (portal + SSH where needed)
- label: Test Data
value: Clean test tenant or lab PBX instance (recommended isolated environment)
preconditions: []
postconditions: []
steps:
- action: Open admin portal or repository URL in browser context
expected: ''
- action: Execute the main verification or configuration action described in the test
expected: ''
- action: Capture evidence (screenshot, log, API response)
expected: ''
- action: Assert expected outcome
expected: ''
automation_status: manual
file: tests/core/virtualization.spec.ts
custom_fields:
original_action: write
manualReason: Requires access to hypervisor networking configuration and virtual switch management
automatable:
- Most UI-driven configuration and verification steps via Playwright
notYet:
- Requires access to hypervisor networking configuration and virtual switch management
- Hypervisor-level operations (vCenter, libvirt, vSphere) not reachable from browser automation
- Long-running load or HA failover scenarios need dedicated lab infrastructure