wup/wup.yaml at main · semcod/wup · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
# WUP Configuration for CLI Testing
# Generated automatically by wup init-cli
# Project: c2004

project:
  name: c2004
  description: Auto-generated config for c2004
watch:
  paths:
  - wup/**
  exclude_patterns:
  - '*.md'
  - '*.txt'
  - tests/**
  - node_modules/**
  file_types: []
services:
- name: iter1-api
  type: web
  paths: []
  root: ''
  quick_tests:
    scope: read
    max_endpoints: 3
  detail_tests:
    scope: all
    max_endpoints: 10
- name: iter1-shell
  type: shell
  paths: []
  root: ''
  quick_tests:
    scope: all
    max_endpoints: 3
  detail_tests:
    scope: all
    max_endpoints: 10
- name: iter7-auto
  type: web
  paths: []
  root: ''
  quick_tests:
    scope: read,write
    max_endpoints: 5
  detail_tests:
    scope: all
    max_endpoints: 10
- name: iter7-shell
  type: shell
  paths: []
  root: ''
  quick_tests:
    scope: all
    max_endpoints: 5
  detail_tests:
    scope: all
    max_endpoints: 10
- name: wup-shell
  type: shell
  paths: []
  root: /home/tom/github/semcod/wup
  quick_tests:
    scope: all
    max_endpoints: 1
  detail_tests:
    scope: all
    max_endpoints: 2
test_strategy:
  quick:
    debounce_s: 2
    max_queue: 5
    timeout_s: 10
  detail:
    debounce_s: 10
    max_queue: 1
    timeout_s: 30
testql:
  scenario_dir: testql-scenarios
  smoke_scenario: iter1-api-v3-smoke.testql.toon.yaml
  output_format: json
  probe_interval_s: 0

# BEGIN WUP MONITORING MANIFEST (auto-generated — do not edit; run: wup sync-testql --write)
monitoring:
  generated_at: '2026-05-26T10:37:26Z'
  generated_by: wup sync-testql --write (or wup watch startup)
  how_to_refresh: wup sync-testql . --write
  probe_interval_s: 60
  health_scenario: ''
  base_url: (set testql.base_url or WUP_BASE_URL)
  endpoint_discovery: true
  scenario_dir: testql-scenarios
  service_map_globs: []
  docker_compose_files: []
  wup_services:
    iter1-api:
      wup_paths: []
      docker: []
      live_probes: []
      testql_dry_run_scenarios: []
    iter1-shell:
      wup_paths: []
      docker: []
      live_probes: []
      testql_dry_run_scenarios: []
    iter7-auto:
      wup_paths: []
      docker: []
      live_probes: []
      testql_dry_run_scenarios: []
    iter7-shell:
      wup_paths: []
      docker: []
      live_probes: []
      testql_dry_run_scenarios: []
    wup-shell:
      wup_paths: []
      docker: []
      live_probes: []
      testql_dry_run_scenarios: []
  docker_not_mapped_to_wup: []
  troubleshooting:
    probe_failed_check:
    - Czy kontener z sekcji docker jest uruchomiony (docker ps)?
    - Czy host_ports mapuje na URL w live_probes (np. 8100 vs 8202)?
    - Czy błąd dotyczy proxy frontendu (/firmware na :8100) vs bezpośredniego :8202?
    - 'Czy endpoint jest w live_probes — jeśli nie, uruchom: wup sync-testql . --write'
    config_vs_runtime: Pole live_probes to faktyczne żądania HTTP WUP. Jeśli endpointu
      tu nie ma, WUP go nie sprawdza — to błąd konfiguracji, nie aplikacji.
# END WUP MONITORING MANIFEST