Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Testing
| Question | Answer |
|---|---|
| Regression Testing | Verify that changes/fixes didn't break previously working functionality. Re-test all features after ECU SW update |
| Smoke Testing | Basic check: does software/system run at all? Vehicle boots up, ECUs respond on bus |
| Sanity Testing | Narrow, focused check after small change Confirm headlight patch fixed only that bug |
| Exploratory Testing | Tester explores system to find defects Try random sequences on infotainment |
| Static Testing | Analysis without running code (reviews, walkthroughs) Code review for AUTOSAR compliance |
| Dynamic Testing | Test by executing the software Run body control module in test bench |
| Black-Box Testing | Test without knowledge of internal implementation Verify seat heating works as spec |
| White-Box Testing | Test with internal code knowledge Check every code branch for safety logic |
| Grey-Box Testing | Partial code/system knowledge used Know CAN message spec, try special frames |
| Performance Testing | Assess speed, response, efficiency Response time of automatic emergency brake |
| Stress Testing | Push system to/beyond limits Send many CAN messages, see buffer limits |
| Load Testing | Test with expected/peak loads Many sensors streaming data to gateway ECU |
| Functional Testing | Verifica que el sistema haga lo correcto (“¿Hace lo que debe?”). Ej.: ¿La luz se enciende si pulso el botón? |
| Usability Testing | Check if system is user-friendly Actual drivers test in-car UI |
| Security Testing | Identify vulnerabilities Simulate CAN message spoofing/hacking |
| Recovery Testing | Evaluate recovery after failure Disconnect/restore battery, test recovery |
| Alpha/Beta Testing | Early/prototype (alpha), late-user (beta) feedback Test prototype in-lab, then pre-release fleet |
| Boundary Value Analysis | Test edges/min/max just inside/outside input range |
| Equivalence Partitioning | Split inputs into groups/partitions with same behavior Speed <0, 0–120, >120 km/h |
| Decision Table Testing | Define logic table with all input/output combos |
| State Transition Testing | Test valid/invalid transitions between states Door lock: locked→unlocked→alarm |
| Statement Testing | Execute each code line at least once ECU code: check all statements run |
| Branch Testing | Execute each decision branch (if/else/switch) |
| Path Testing | Execute all unique code paths (complex, many) |
| Condition Testing | Test each boolean condition as true/false Test brake signal on/off logic |
| VERIFY | ¿Estoy construyendo el producto correctamente? Revisa si el producto cumple con las especificaciones y requisitos técnicos/diseño. |
| VALIDATE | ¿Estoy construyendo el producto correcto? Revisa si el producto cumple el propósito y las necesidades reales del usuario/cliente. |
| Corner Case Testing | Buscar condiciones extremas o poco probables que no se cubrieron en test cases formales. Ejemplo: Encender y apagar el motor repetidamente mientras se programan ventanas; dejar el coche bajo intermitente + abrir y cerrar puertas rápidamente. |
Created by:
yizuztineo