fixed pytest build environment issues

Author: Saumya-R

feature_integration_tests/LIFECYCLE_TESTS_SUMMARY.md

@@ -45,7 +45,7 @@ Tests run with an actual Launch Manager daemon instance. This validates:
 
 This test suite covers **85 of 92 lifecycle requirements** from the S-CORE Platform specification (**92% coverage**). The tests validate API integration patterns for both Rust and C++ implementations.
 
-> **Note**: All tests should be run using Bazel. Direct pytest execution is a work in progress.
+> **Note**: Tests can be executed with both Bazel and direct pytest. Bazel is recommended for CI; pytest is supported for local development and debugging.
 
 **Coverage by Category:**
 
@@ -440,6 +440,43 @@ bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_daem
 bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_daemon_cpp
 ```
 
+**Run lifecycle tests with pytest (local):**
+
+```bash
+# All lifecycle tests (Rust + C++)
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ -q -v
+
+# Rust only
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ -q -v -m rust
+
+# C++ only
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ -q -v -m cpp
+```
+
+**Build scenario executables from pytest:**
+
+```bash
+# Build with default Bazel config (linux-x86_64)
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ \
+  --build-scenarios \
+  --build-scenarios-timeout=600 \
+  -q -v
+
+# Build with explicit Bazel config
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ \
+  --build-scenarios \
+  --bazel-config=linux-x86_64 \
+  --build-scenarios-timeout=600 \
+  -q -v
+
+# Or via environment override
+FIT_BAZEL_CONFIG=linux-x86_64 \
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ \
+  --build-scenarios \
+  --build-scenarios-timeout=600 \
+  -q -v
+```
+
 ### Quick Start
 
 #### API Integration Tests (Fast, No Daemon Required)
@@ -472,6 +509,18 @@ bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_cpp
   --test_filter="*test_process_launching*"
 ```
 
+**Using pytest (direct local run):**
+
+```bash
+# Full lifecycle API-mode set
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ -q -v
+
+# Single file
+python3 -m pytest \
+  feature_integration_tests/test_cases/tests/lifecycle/test_process_launching.py \
+  -q -v
+```
+
 #### Daemon Integration Tests (End-to-End Validation)
 
 **Using Bazel:**
@@ -485,6 +534,21 @@ bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_daem
 bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_daemon_rust --test_output=all
 ```
 
+**Using pytest (direct local run):**
+
+```bash
+# Daemon integration file (Rust + C++)
+python3 -m pytest \
+  feature_integration_tests/test_cases/tests/lifecycle/test_process_launching_with_daemon.py \
+  -q -v
+```
+
+Local daemon fixture notes:
+
+- The fixture builds required binaries with Bazel using `--config=linux-x86_64` by default.
+- Override Bazel config with `FIT_BAZEL_CONFIG` when needed.
+- The fixture prepares required flatbuffer config binaries automatically.
+
 ### Understanding Build Configurations
 
 **Bazel `--config` flag:**
@@ -600,6 +664,7 @@ When running daemon integration tests, the Launch Manager requires a configurati
   },
   "initial_run_target": "startup"
 }
+```
 
 ## Dependencies
 
@@ -625,12 +690,12 @@ When running daemon integration tests, the Launch Manager requires a configurati
 Potential areas for expansion:
 
 1. **Enhanced Daemon Integration**:
-   - ✅ Basic daemon fixture and test infrastructure
-   - ✅ Supervised application launching tests
-   - ⏳ Dynamic configuration updates via control interface
-   - ⏳ Comprehensive health monitoring validation
-   - ⏳ Multi-daemon distributed scenarios
-   - ⏳ Performance metrics collection (timing, resource usage)
+   - Basic daemon fixture and test infrastructure
+   - Supervised application launching tests
+   - Dynamic configuration updates via control interface
+   - Comprehensive health monitoring validation
+   - Multi-daemon distributed scenarios
+   - Performance metrics collection (timing, resource usage)
 
 2. **Additional Test Scenarios**:
    - Process termination and cleanup validation
@@ -667,4 +732,4 @@ Potential areas for expansion:
 
 ---
 
-**Summary**: This test suite covers 85 of 92 lifecycle requirements (92% coverage) and validates API integration patterns for both Rust and C++ implementations. Tests run with Bazel for both API integration mode (fast CI feedback) and daemon integration mode (comprehensive end-to-end validation). The dual-language implementation ensures both ecosystems have equal support and validates that lifecycle APIs work correctly across languages.
+**Summary**: This test suite covers 85 of 92 lifecycle requirements (92% coverage) and validates API integration patterns for both Rust and C++ implementations. Tests can run with Bazel (recommended for CI) and with direct pytest (recommended for local debugging) for both API integration and daemon integration modes. The dual-language implementation ensures both ecosystems have equal support and validates that lifecycle APIs work correctly across languages.

feature_integration_tests/README.md

@@ -19,6 +19,22 @@ This directory contains Feature Integration Tests for the S-CORE project. It inc
   - `test_ssh.py` — SSH connectivity tests
 - `configs/` — Configuration files for ITF execution (DLT, QEMU bridge, etc.)
 
+## Lifecycle FIT Summary
+
+Lifecycle Feature Integration Tests validate end-to-end integration patterns for the S-CORE lifecycle stack across Rust and C++ scenarios.
+
+- Coverage: 85/92 lifecycle requirements (92%)
+- Modes:
+  - API integration mode (no running daemon required)
+  - Daemon integration mode (real Launch Manager behavior)
+- Main validated areas:
+  - Process launching and dependency ordering (sequential/parallel)
+  - Conditional launching and run targets
+  - Process security/resources/termination
+  - Monitoring, recovery, control interface, logging, and configuration handling
+
+For full lifecycle requirement mapping and detailed rationale, see `feature_integration_tests/LIFECYCLE_TESTS_SUMMARY.md`.
+
 ## Running Tests
 
 ### Python Test Cases (scenario-based FIT)
@@ -36,6 +52,57 @@ bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_rust
 bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_cpp
 ```
 
+To run daemon integration test suites:
+
+```sh
+bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_daemon_rust
+bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_daemon_cpp
+```
+
+To run lifecycle-focused tests only:
+
+```sh
+bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_rust --test_filter="*lifecycle*"
+bazel test --config=linux-x86_64 //feature_integration_tests/test_cases:fit_cpp --test_filter="*lifecycle*"
+```
+
+Pytest direct local runs are also supported:
+
+```sh
+# All lifecycle tests (rust + cpp)
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ -q -v
+
+# Rust only
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ -q -v -m rust
+
+# C++ only
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ -q -v -m cpp
+```
+
+To build scenario executables from pytest before running tests:
+
+```sh
+# Default Bazel config: linux-x86_64
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ \
+  --build-scenarios \
+  --build-scenarios-timeout=600 \
+  -q -v
+
+# Explicit Bazel config
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ \
+  --build-scenarios \
+  --bazel-config=linux-x86_64 \
+  --build-scenarios-timeout=600 \
+  -q -v
+
+# Or via environment override
+FIT_BAZEL_CONFIG=linux-x86_64 \
+python3 -m pytest feature_integration_tests/test_cases/tests/lifecycle/ \
+  --build-scenarios \
+  --build-scenarios-timeout=600 \
+  -q -v
+```
+
 ### ITF Tests (QEMU-based)
 
 ITF tests run on a QEMU target and require the `itf-qnx-x86_64` config:

feature_integration_tests/test_cases/BUILD

@@ -12,6 +12,7 @@
 # *******************************************************************************
 load("@pip_score_venv_test//:requirements.bzl", "all_requirements")
 load("@rules_python//python:pip.bzl", "compile_pip_requirements")
+load("@score_lifecycle_health//:defs.bzl", "launch_manager_config")
 load("@score_tooling//python_basics:defs.bzl", "score_py_pytest")
 
 # In order to update the requirements, change the `requirements.txt` file and run:
@@ -34,6 +35,11 @@ compile_pip_requirements(
     ],
 )
 
+launch_manager_config(
+    name = "daemon_lifecycle_configs",
+    config = "//feature_integration_tests/test_cases/configs:daemon_launch_manager_config.json",
+)
+
 # Tests targets
 score_py_pytest(
     name = "fit_rust",

feature_integration_tests/test_cases/configs/BUILD

@@ -0,0 +1,27 @@
+# *******************************************************************************
+
+# Copyright (c) 2026 Contributors to the Eclipse Foundation
+
+#
+
+# See the NOTICE file(s) distributed with this work for additional
+
+# information regarding copyright ownership
+
+#
+
+# This program and the accompanying materials are made available under the
+
+# terms of the Apache License Version 2.0 which is available at
+
+# <https://www.apache.org/licenses/LICENSE-2.0>
+
+#
+
+# SPDX-License-Identifier: Apache-2.0
+
+# *******************************************************************************
+
+exports_files([
+    "daemon_launch_manager_config.json",
+])

feature_integration_tests/test_cases/configs/daemon_launch_manager_config.json

@@ -0,0 +1,119 @@
+{
+    "schema_version": 1,
+    "defaults": {
+        "deployment_config": {
+            "bin_dir": "bin/",
+            "ready_recovery_action": {
+                "restart": {
+                    "number_of_attempts": 1,
+                    "delay_before_restart": 0.5
+                }
+            }
+        },
+        "component_properties": {
+            "application_profile": {
+                "application_type": "Reporting",
+                "is_self_terminating": false,
+                "alive_supervision": {
+                    "reporting_cycle": 0.1,
+                    "min_indications": 1,
+                    "max_indications": 3,
+                    "failed_cycles_tolerance": 1
+                }
+            },
+            "depends_on": [],
+            "process_arguments": [],
+            "ready_condition": {
+                "process_state": "Running"
+            }
+        },
+        "run_target": {
+            "transition_timeout": 5,
+            "recovery_action": {
+                "switch_run_target": {
+                    "run_target": "fallback_run_target"
+                }
+            }
+        },
+        "alive_supervision": {
+            "evaluation_cycle": 0.5
+        }
+    },
+    "components": {
+        "state_manager": {
+            "description": "State Manager application",
+            "component_properties": {
+                "binary_name": "control_daemon",
+                "application_profile": {
+                    "application_type": "State_Manager",
+                    "alive_supervision": {
+                        "min_indications": 0
+                    }
+                },
+                "depends_on": []
+            }
+        },
+        "cpp_supervised_app": {
+            "component_properties": {
+                "binary_name": "cpp_supervised_app",
+                "application_profile": {
+                    "application_type": "Reporting_And_Supervised"
+                },
+                "process_arguments": [
+                    "-d50"
+                ]
+            },
+            "deployment_config": {
+                "environmental_variables": {
+                    "PROCESSIDENTIFIER": "cpp_supervised_app",
+                    "CONFIG_PATH": "etc/hmproc_cpp_supervised_app.bin",
+                    "IDENTIFIER": "cpp_supervised_app"
+                }
+            }
+        },
+        "rust_supervised_app": {
+            "component_properties": {
+                "binary_name": "rust_supervised_app",
+                "application_profile": {
+                    "application_type": "Reporting_And_Supervised"
+                },
+                "process_arguments": [
+                    "-d50"
+                ]
+            },
+            "deployment_config": {
+                "environmental_variables": {
+                    "PROCESSIDENTIFIER": "rust_supervised_app",
+                    "CONFIG_PATH": "etc/hmproc_rust_supervised_app.bin",
+                    "IDENTIFIER": "rust_supervised_app"
+                }
+            }
+        }
+    },
+    "run_targets": {
+        "Startup": {
+            "description": "Minimal functionality of the system",
+            "depends_on": [
+                "cpp_supervised_app",
+                "rust_supervised_app",
+                "state_manager"
+            ],
+            "recovery_action": {
+                "switch_run_target": {
+                    "run_target": "fallback_run_target"
+                }
+            }
+        }
+    },
+    "initial_run_target": "Startup",
+    "fallback_run_target": {
+        "description": "Switching off everything",
+        "depends_on": [
+            "state_manager"
+        ],
+        "transition_timeout": 1.5
+    },
+    "alive_supervision": {
+        "evaluation_cycle": 0.5
+    }
+}