ZTABS provides quality assurance and testing services for Houston's safety-critical and compliance-intensive industries — aerospace software testing for NASA Johnson Space Center contractors and Houston's defense and space companies where software defects in flight systems, mission control applications, and spacecraft subsystems can endanger crew lives and destroy billions in hardware, energy SCADA and industrial control system testing for Houston's pipeline operators, refinery operators, and upstream producers where software failures in supervisory control systems can cause environmental releases, equipment damage, and worker safety incidents, and healthcare application testing for Texas Medical Center institutions where software defects can affect patient safety, clinical decision-making, and HIPAA compliance across the world's largest medical complex.
Houston is not a city where you can ship software bugs and fix them later. The industries that drive Houston's economy — aerospace, energy, and healthcare — operate in environments where software failure has consequences far beyond user inconvenience. A bug in a consumer app loses a user. A bug in a spacecraft flight controller can lose a crew. A bug in a pipeline SCADA system can cause an environmental disaster. A bug in a clinical decision support tool can harm a patient. QA testing in Houston must meet the standards of industries where software is literally life-or-death. Aerospace testing rigor: Houston is the center of human spaceflight — NASA Johnson Space Center manages astronaut training, mission control, and the International Space Station program. Boeing, Lockheed Martin, SpaceX, Axiom Space, and dozens of other aerospace companies operate in Houston. Software for spacecraft, launch vehicles, and ground systems must meet NASA's NPR 7150.2 software engineering requirements and the DO-178C standard for airborne systems. Testing for aerospace software is not optional or cursory — it's a regulated activity with specific coverage requirements, documented test procedures, independent verification, and traceable test results. Test documentation alone can constitute 40-60% of the software development effort in safety-critical aerospace systems. Energy testing requirements: Houston energy companies operate critical infrastructure — pipelines carrying natural gas and hazardous liquids, refineries processing crude oil at high temperatures and pressures, and offshore platforms in extreme environments. The software controlling this infrastructure (SCADA systems, distributed control systems, safety instrumented systems) must function correctly under all conditions, including failure scenarios. PHMSA requires pipeline operators to implement and test their control room management procedures, including SCADA system alarm management and human factors. API 1164 provides cybersecurity standards for pipeline SCADA systems. Testing for energy control systems must verify not just normal operation but degraded-mode operation, failover scenarios, alarm management, and cybersecurity resilience. Healthcare testing stakes: software used in patient care at TMC institutions must function reliably in clinical workflows. A bug in a medication dosing calculator could result in a harmful dose. A bug in a patient matching algorithm could result in wrong-patient errors. A bug in a lab result display could show incorrect values leading to wrong clinical decisions. Healthcare software testing must cover functional correctness, usability in clinical workflows, HIPAA compliance for data handling, interoperability with EMR systems, and accessibility for clinical users working under time pressure. FDA regulations (21 CFR Part 820) apply to software classified as medical devices, adding design control and validation requirements.
Houston's QA testing demand spans aerospace, energy, healthcare, and enterprise software. Aerospace Software Testing: flight software testing (testing software that runs on spacecraft — guidance, navigation, and control (GNC) algorithms, vehicle management systems, crew display systems, environmental control, and communication systems — testing follows structured methodologies: requirements-based testing (every software requirement has at least one test), structural coverage analysis (every code path executed during testing), stress testing (system behavior under maximum computational load), and fault injection testing (system behavior when hardware components fail or provide erroneous data) — for Houston aerospace: flight software testing requires independent verification and validation (IV&V) — the test team must be organizationally independent from the development team — test documentation follows NASA standards including test procedures, test reports, discrepancy reports, and test coverage analysis), ground system testing (testing software that supports mission operations from the ground — mission control displays, telemetry processing, command and control systems, planning and scheduling tools, and communication systems — ground system testing includes real-time performance testing (ensuring telemetry is processed and displayed within timing requirements), multi-user testing (mission control teams may have dozens of operators using the system simultaneously), and integration testing with flight software (verifying that ground commands produce correct spacecraft responses in simulation environments) — for Houston: JSC's Mission Control Center and its supporting contractor facilities are the primary ground system testing environments), and simulation testing (testing software within high-fidelity simulation environments — man-in-the-loop simulations where astronauts and flight controllers operate the software in simulated mission scenarios — simulation testing validates that the software supports human operators effectively under nominal and contingency conditions — for Houston aerospace: simulation testing at JSC involves integrated simulations that combine flight software, ground software, and human operators in end-to-end mission scenario testing)). Energy Control System Testing: SCADA system testing (testing supervisory control and data acquisition systems for Houston pipeline operators and facility operators — functional testing (data acquisition from field devices, alarm processing, control command execution, historian data recording), performance testing (system response time under maximum data load — SCADA systems may process thousands of data points per second), failover testing (system behavior when primary servers fail — SCADA systems must maintain monitoring and control through hardware failures), alarm testing (verifying alarm setpoints, priorities, and escalation — proper alarm management is a PHMSA requirement for pipeline operators — alarm flooding during upset conditions is a common SCADA deficiency), and cybersecurity testing (verifying SCADA system resilience against network-based attacks per API 1164 and NIST CSF recommendations) — for Houston energy: SCADA testing must be performed carefully to avoid disrupting live operations — we test in staging environments that replicate the production SCADA configuration), safety instrumented system (SIS) testing (testing the safety systems that prevent hazardous conditions in refineries and chemical plants — SIS testing follows IEC 61511 (process industry safety systems) — testing verifies that safety functions (emergency shutdown, pressure relief, gas detection response) execute correctly and within required response times — proof testing validates that SIS components (sensors, logic solvers, final elements) are functioning correctly — for Houston petrochemical: SIS testing is a regulatory requirement with documented intervals and coverage requirements), and control system integration testing (testing the integration between SCADA, DCS (distributed control systems), SIS, and business systems (ERP, production accounting, energy management) — integration testing verifies data flows correctly between systems and that control actions in one system produce appropriate responses in connected systems — for Houston energy: the integration landscape is complex — a refinery may have multiple DCS systems from different vendors (Honeywell, Emerson, ABB, Yokogawa) integrated with corporate SCADA and ERP systems)). Healthcare Application Testing: clinical application testing (testing applications used in patient care — EMR customizations, clinical decision support tools, medication management systems, and patient monitoring applications — clinical testing includes functional testing (the application performs correct clinical calculations, displays correct patient data, and executes correct clinical workflows), usability testing (clinicians can use the application effectively under realistic clinical conditions — time pressure, interruptions, multiple patients), safety testing (the application does not facilitate wrong-patient, wrong-medication, or wrong-dose errors), and interoperability testing (the application correctly exchanges data with Epic/Cerner via HL7 FHIR or other interfaces) — for TMC institutions: clinical application testing must involve clinical end users who can evaluate whether the application supports or hinders their clinical workflow), HIPAA compliance testing (testing applications for HIPAA security and privacy compliance — access control testing (only authorized users can access PHI), encryption testing (PHI is encrypted at rest and in transit), audit logging testing (all PHI access is logged), session management testing (sessions timeout after inactivity), and minimum necessary testing (users can only access the PHI needed for their role) — for Houston healthcare: HIPAA compliance testing is required before any application handles patient data — OCR (Office for Civil Rights) enforcement actions for HIPAA violations have resulted in settlements exceeding $10M for major healthcare systems), and FDA validation testing (testing software classified as medical devices per FDA regulations — following IEC 62304 software lifecycle and 21 CFR Part 820 design control requirements — validation testing includes intended use testing, risk-based testing (testing focused on hazards identified in the risk analysis), installation qualification, operational qualification, and performance qualification — for Houston medical device companies: FDA validation documentation is reviewed during premarket submissions and facility inspections))). Enterprise Software Testing: performance testing (load testing, stress testing, and endurance testing for Houston enterprise applications — determining maximum user capacity, response time under load, and stability during sustained operation — for Houston energy companies: enterprise applications must perform reliably during operationally critical periods (month-end close, regulatory reporting deadlines, emergency response) when usage spikes and failure is not acceptable), regression testing (automated regression test suites that verify existing functionality is preserved when changes are made — for Houston enterprises with large application portfolios: automated regression testing enables continuous deployment confidence — changes can be released with assurance that existing workflows still function), and security testing (penetration testing, vulnerability assessment, and security code review for Houston enterprise applications — for Houston energy: cybersecurity testing is increasingly important as energy companies face state-sponsored and criminal cyber threats targeting operational technology and corporate systems — TSA Security Directives for pipeline operators now require specific cybersecurity measures).
Our QA testing approach for Houston balances industry-specific rigor with practical efficiency. Phase 1 — Test Strategy Development (1-2 weeks): planning the testing approach: risk-based test planning (identifying the highest-risk areas of the application and focusing testing effort there — for aerospace: risks are defined by the software's criticality level (how the software can affect crew safety, mission success, and vehicle integrity) — for energy: risks are defined by the potential consequences of software failure (environmental release, equipment damage, worker injury) — for healthcare: risks are defined by the patient safety impact of software defects — risk-based planning ensures testing resources are allocated to the areas where defects have the greatest consequences), standards mapping (identifying applicable testing standards and mapping test activities to standard requirements — for aerospace: mapping to NASA NPR 7150.2 and DO-178C — for energy: mapping to IEC 61511, API 1164, and PHMSA requirements — for healthcare: mapping to IEC 62304, 21 CFR Part 820, and HIPAA — standards mapping ensures testing satisfies regulatory and contractual requirements), test environment planning (defining the test environments needed — for aerospace: simulation environments that replicate flight hardware interfaces — for energy: SCADA test environments that replicate field device configurations — for healthcare: EMR integration test environments with test patient data — test environment fidelity directly affects the validity of test results — testing on environments that don't match production configurations produces unreliable results), and automation strategy (determining which tests to automate and which to execute manually — for Houston's safety-critical applications: automation is used for regression testing and repetitive verification, but critical safety testing often requires manual execution with human judgment — the automation strategy balances efficiency with the need for human assessment in areas where automated oracles are insufficient)). Phase 2 — Test Development (2-4 weeks): creating test artifacts: test case design (developing detailed test cases — for safety-critical applications: each test case includes preconditions, step-by-step procedures, expected results, and pass/fail criteria — test cases trace to requirements (every requirement has at least one test case) and to risk analysis results (high-risk areas have more extensive test coverage) — for Houston aerospace: test procedures are formal documents that are reviewed, approved, and placed under configuration management), test data management (creating and managing test data — for healthcare: test data must include realistic clinical scenarios without using actual patient data — synthetic patient records with realistic demographics, clinical histories, and data patterns — for energy: test data must include realistic SCADA data patterns including alarm conditions, communication failures, and simultaneous multiple data point changes — for all Houston testing: test data management includes procedures for creating, maintaining, and securing test data), and test automation development (building automated test scripts — for Houston enterprise: we use established automation frameworks (Selenium, Playwright, Cypress for web applications, Appium for mobile, custom frameworks for SCADA and embedded systems) — automation scripts include proper error handling, logging, and reporting — automated tests are maintained as part of the codebase with the same version control and review processes applied to production code)). Phase 3 — Test Execution and Reporting (ongoing): running tests and communicating results: structured test execution (executing tests according to the test plan — for safety-critical applications: test execution is a documented activity — each test execution is recorded with the date, tester, environment, results, and any deviations from the procedure — for Houston aerospace: test execution may require witness signatures and independent review of results), defect management (managing identified defects through a structured lifecycle — defect reporting with severity and priority classification, root cause analysis for critical defects, fix verification, and regression testing to ensure fixes don't introduce new defects — for Houston's safety-critical industries: defect resolution follows formal processes with review boards and documented decisions for severity classification and fix prioritization), and compliance documentation (producing the testing documentation required by regulatory and contractual obligations — for aerospace: test reports, requirements traceability matrices, structural coverage analysis, and discrepancy reports — for energy: SIS proof test reports, alarm management test results, and cybersecurity test reports — for healthcare: validation reports, HIPAA compliance test results, and FDA submission-ready documentation — for Houston: testing documentation is often as important as the testing itself — regulators and auditors evaluate the documentation).
Aerospace / NASA Flight Software Validation
A Houston aerospace contractor developing flight software for a NASA human spaceflight program needed to expand its testing capability to meet the program's aggressive schedule. The software — a vehicle management system (VMS) controlling spacecraft subsystems including propulsion, thermal control, power management, and environmental control and life support (ECLSS) — had approximately 420,000 lines of C++ code executing on redundant flight computers. The testing challenge: NASA NPR 7150.2D (NASA Software Engineering Requirements) classified this software as Class A — the highest criticality level, meaning software failure could result in loss of crew or loss of mission. Class A testing requirements included: 100% requirements-based test coverage (every software requirement verified by at least one test), structural coverage analysis (statement coverage, branch/decision coverage, and modified condition/decision coverage (MC/DC) — the most rigorous structural coverage criterion, requiring that every condition in every decision is shown to independently affect the decision's outcome), independent verification and validation (the test team was organizationally independent from the development team with separate reporting chains to the program manager), formal test procedures (each test case was a reviewed and approved document with step-by-step procedures, expected results, and pass/fail criteria), and traceable defect resolution (every defect tracked from discovery through root cause analysis, fix implementation, fix verification, and regression testing, with traceability to the requirement or design element affected). The staffing problem: the contractor's existing test team of 8 engineers was qualified but undersized for the testing volume. The VMS had 3,247 software requirements generating approximately 5,800 test cases. At the current team's execution rate, completing the required testing would take 14 months — but the program schedule required testing completion in 8 months to support the integrated vehicle testing phase. The contractor needed to nearly double testing throughput without compromising NASA's quality requirements. Previous attempts to add staff from other programs had failed because the engineers lacked familiarity with the VMS software architecture, the test environment (a hardware-in-the-loop simulation with flight computer emulators and subsystem simulators), and NASA's testing process requirements.
We embedded a team of 6 test engineers into the contractor's test organization for a 9-month engagement. Month 1 — Qualification and Environment Familiarization: our engineers completed a structured qualification program: VMS software architecture training (2 weeks — understanding the software's modular architecture, inter-module communication, real-time scheduling, and redundancy management — essential for designing effective test cases and interpreting test results), test environment certification (1 week — achieving certification to operate the hardware-in-the-loop (HIL) test environment — the HIL lab contained flight computer emulators, subsystem simulators (propulsion, thermal, power, ECLSS), and network simulators replicating the spacecraft's data bus — operating this environment required understanding the simulation architecture, initialization procedures, and known simulation limitations), and NASA process compliance training (1 week — understanding NPR 7150.2D requirements, the program's software management plan, the test procedures format and review process, the defect reporting and tracking system (JIRA configured for NASA process compliance), and the configuration management procedures for test artifacts). Months 2-8 — Test Execution Campaign: our team executed testing in parallel with the existing team, working from the approved test plan and test procedures. Testing was organized by VMS subsystem. Propulsion control testing: 847 test cases covering engine ignition sequencing, thrust vector control, propellant management, and abort scenarios — testing required coordinating propulsion subsystem simulator states with VMS software commands and verifying response timing (propulsion commands must execute within 20ms of the control law computation cycle) — we identified 23 defects during propulsion testing, including 2 critical defects: one where the abort sequence timing violated the requirement under a specific failure combination (two engines failed simultaneously with a communication bus fault), and one where propellant tank isolation valve commanding had a race condition under high-rate maneuvering. Thermal control testing: 612 test cases covering active thermal control (coolant loop management), heater control, radiator deployment, and thermal protection during atmospheric entry — thermal testing required long-duration simulations (orbital thermal cycles are 90 minutes, and some thermal requirements involved behavior over multiple orbital periods) — testing identified 14 defects including one where the heater control algorithm failed to prevent freezing in a specific spacecraft orientation during eclipse (the thermal model in the software used a simplified view factor calculation that was inaccurate for extreme attitudes). Power management testing: 534 test cases covering solar array management, battery charge/discharge control, power bus management, and load shedding priority — power testing included nominal operations and degraded scenarios (partial solar array failure, battery cell failures, increased load from contingency operations) — identified 11 defects including one where load shedding priority was incorrectly implemented during a scenario combining high power demand from the thermal system during reentry preparation with a partially failed battery. ECLSS testing: 489 test cases covering atmospheric revitalization (CO2 removal, O2 generation), temperature and humidity control, and fire detection and response — ECLSS testing was particularly important for crew safety and required testing over extended durations to verify atmospheric control stability — identified 8 defects including one where the CO2 removal system's control algorithm had an oscillation mode under specific crew activity patterns (simultaneous exercise by multiple crew members). Redundancy management testing: 1,180 test cases covering fault detection, isolation, and recovery (FDIR) across all subsystems — redundancy testing systematically injected faults (sensor failures, actuator failures, communication failures, computer failures) and verified that the VMS correctly detected the fault, isolated the failed component, and recovered using redundant hardware — this was the most complex testing area because the combinations of possible faults were enormous — we used combinatorial testing techniques to achieve efficient coverage — identified 31 defects in FDIR, many involving multi-fault scenarios where the recovery from one fault interfered with the detection or recovery of a subsequent fault. Integration testing: 138 cross-subsystem test cases verifying interactions between VMS subsystems — propulsion-thermal interactions during engine firing, power-ECLSS interactions during load shedding, and overall system behavior during complex mission phases (rendezvous, docking, undocking, deorbit, entry) — integration testing identified 7 defects, most involving timing interactions between subsystems that weren't visible during individual subsystem testing. Structural Coverage Analysis: after requirements-based testing was complete, we performed structural coverage analysis to identify code that was not exercised by the test suite. For MC/DC coverage: we analyzed every decision point in the code and designed additional test cases to achieve the required coverage. We achieved 98.7% MC/DC coverage — the remaining 1.3% was analyzed and documented as dead code or defensive code paths that could not be reached under valid inputs (NASA allows this with justification). Defect Resolution Support: for each defect identified, our team provided: a detailed defect report with steps to reproduce, analysis of the root cause and affected requirements, verification testing after the development team implemented fixes, and regression testing to confirm fixes didn't introduce new problems. Total defects identified by our team: 94 (out of 127 total program defects identified during the testing phase). Critical defects: 7. All defects resolved and verified before testing completion.
The test campaign completed on schedule — 8 months from test execution start, meeting the program's integrated vehicle testing milestone. Testing throughput: the combined 14-engineer test team (8 existing + 6 ZTABS) executed 5,800 test cases in 7 months of active testing (after 1-month qualification), averaging 830 test cases per month — the original 8-person team had been executing approximately 415 test cases per month, so the ZTABS augmentation achieved the required doubling of throughput. Defect detection: 94 of 127 defects (74%) were identified by the ZTABS team — this proportion was higher than the staffing ratio (43% of the team) because our engineers brought fresh perspective to the software (the existing team had been involved in development and had accumulated assumptions about software behavior that sometimes masked defects). Critical defect identification: the 7 critical defects identified by our team included scenarios that the existing team had not yet tested — multi-fault scenarios and edge cases in timing and control interactions — these defects, if undetected, could have caused mission-critical failures during flight. Coverage achievement: 100% requirements-based test coverage (every requirement verified), 98.7% MC/DC structural coverage (exceeding the 97% program target), and complete test documentation package accepted by NASA IV&V without findings. Schedule impact: testing completed on the original schedule despite the initial staffing shortfall — the program's integrated vehicle testing phase began as planned — the alternative (completing testing 6 months late with the original team) would have delayed the program schedule and incurred estimated delay costs of $8-12M. NASA assessment: the program's NASA technical monitor rated the testing effort as "highly effective" in the post-testing assessment — specifically noting the thoroughness of multi-fault FDIR testing and the quality of defect reporting. Financial summary: ZTABS engagement cost: $1.8M (6 engineers × 9 months). Estimated schedule delay cost avoided: $8-12M. Defect detection value: the 7 critical defects, if discovered during later testing phases (integrated vehicle testing or mission simulation), would have required test campaign rework estimated at $3-5M. Total estimated value: $11-17M in avoided delay and rework costs.
Automated unit, integration, and E2E tests with Jest, Cypress, Playwright, and more.
Exploratory testing, regression, and UAT to validate real-world usage and edge cases.
Load, stress, and scalability tests to ensure apps perform under real traffic.
Tests integrated into your pipeline for continuous feedback on every change.
Test plans, coverage analysis, and risk-based prioritization for efficient QA.
Houston's QA testing market includes aerospace IV&V firms, energy testing specialists, and healthcare validation consultancies. (1) Aerospace IV&V firms — established NASA contractor relationships with deep flight software expertise but often limited availability and high costs. (2) Energy testing specialists — SCADA and control system testing expertise but limited aerospace or healthcare capabilities. (3) Healthcare validation consultancies — FDA validation expertise but limited energy or aerospace knowledge. (4) National QA firms (Cognizant, Infosys testing practices) — scale and process but limited Houston domain expertise. ZTABS provides QA testing across Houston's key industries with engineers who understand both testing methodology and domain-specific requirements.
QA testing services in Houston vary by industry and testing type. Enterprise Application Testing (functional, regression, performance, 4-8 weeks): $80,000-$200,000. Healthcare Application Validation (HIPAA compliance, FDA validation, clinical workflow, 6-12 weeks): $150,000-$400,000. Energy Control System Testing (SCADA, SIS, cybersecurity, 8-16 weeks): $200,000-$500,000. Aerospace Software IV&V (NASA-compliant, full coverage, 6-12 months): $800,000-$2,500,000. Ongoing Testing: $15,000-$50,000/month for continuous testing services. ZTABS delivers at $200-350/hr — test engineers with NASA, energy, and healthcare domain certifications.
Verified reviews from real client engagements — sourced from our public testimonial archive and Clutch profile.
My experience is throughout positive. Communication, service, the short response times and the flawless execution of a challenging topic was absolutely great. ZTABS is definitely my first choice again.
Christian Neff
Bank Software Advisory · Bank Software Advisory
Fintech
Fantastic Agency! I couldn't fault them even if I tried. They always go above and beyond to meet your expectations and always produces quality work. Thank you ZTABS.
Stephanie Kal
CEO · Beauty Finder Australia
Marketplace
It has been great working with ZTABS. They bounce off the ideas along the way. Amazing Experience.
Joel Rowe
CEO · Drill Quoter
Marketplace
We don't just contract. We ship and operate our own software. 23 products in production.
Common questions about qa & testing for Houston businesses
Three fundamental differences: coverage requirements (safety-critical testing requires demonstrable coverage — every requirement tested, every code path exercised, every failure mode examined — consumer software testing can prioritize happy-path testing, but safety-critical testing must systematically address failure scenarios), documentation (testing must produce auditable documentation — test procedures, test results, defect reports, and traceability matrices — this documentation is reviewed by regulators, auditors, and independent assessors — it's not optional), and independence (safety-critical testing often requires organizational independence between development and test teams — the test team reports separately from the development team to ensure testing objectivity — this is a NASA requirement for Class A software and a best practice for energy and healthcare applications).
ZTABS is a remote-first qa & testing agency serving New York businesses — including test automation, manual qa, performance testing. We work with Finance & Fintech, Media & Advertising, Fashion & Retail companies in New York, NY via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
QA & Testing in Los Angeles, CAZTABS is a remote-first qa & testing agency serving Los Angeles businesses — including test automation, manual qa, performance testing. We work with Entertainment & Media, E-commerce & DTC Brands, Gaming & AR/VR companies in Los Angeles, CA via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
QA & Testing in Chicago, ILZTABS is a remote-first qa & testing agency serving Chicago businesses — including test automation, manual qa, performance testing. We work with Finance & Trading, Manufacturing, Transportation & Logistics companies in Chicago, IL via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Development in Houston, TXZTABS is a remote-first web development agency serving Houston businesses — including full-stack development, progressive web apps, api development. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Design in Houston, TXZTABS is a remote-first web design agency serving Houston businesses — including ui/ux design, responsive design, custom interfaces. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
AI Development in Houston, TXZTABS is a remote-first AI development agency serving Houston businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
QA & TestingLearn more about our qa & testing services nationwide.
Partner with ZTABS for expert qa & testing in Houston. Get a free consultation today.
