3. I am …
14+ years experience in Embedded Systems and SW Engineering
SECC, Valeo, Toshiba
Co-founder of Swift Act Services
ISTQB Advanced Full certified
https://eg.linkedin.com/in/amrali
Track records in 4 continents and 12 countries
Reviewed 3 books
6. Test Levels
A point in the development
model where testing is done.
A development model can have
more than a test level depending
on the model and the project.
12. System Testing
Testing the system as a whole
End-to-end behavior is the focus.
Usually carried by independent test team
13. Acceptance Testing
Goal is to establish confidence in the system; not to find bugs.
Usually done by customers or system users or any other stakeholders
Asses the readiness of the system for deployment or use
Test forms:
UAT
OAT
Contract/Regulation AT
Alpha or Beta
18. Problem Space
Myth: Structure techniques are used
for low test levels.
Myth: Non-functional test is done @
higher levels.
Fact: Every test technique and test
type is applicable @ every test level.
You need to find your position in the
testing grid.
19. Selecting and Combining Techniques
Techniques must be combined.
Combined techniques are more powerful than trying to find a single “best” technique.
When techniques are combined, test cases should cover all applicable coverage criteria.
To select techniques, consider:
Applicability
Limitations and difficulties
Coverage goals
Defects typically detected
20. Different Embedded SW Testing Jobs
Embedded
SW Testing
Embedded
SW
Validation
Embedded
Systems
Validation
Programming C is a must Yes, any Yes, any
Microcontrollers Yes Yes Yes
Testing Techniques Yes Yes Yes
Unit Testing Yes No No
Integration Testing Yes No No
System Testing May be Yes Yes
Acceptance Testing May be May be Yes
27. Swift Act LLC offers
Mini Embedded SW Testing 101 x 2 days
Embedded SW Testing 101 x 4 days
Contacts:
www.swift-act.com
training@swift-act.com
https://www.facebook.com/groups/EmbeddedSystemsTraining/
Testing a component in isolation.
Driver + Component + Stubs
<number>
Integration Testing = Testing interfaces and interactions between different components
<number>
Top-down To verify new architectures
Bottom-up To verify new building blocks
<number>
Minimum capability AR stacks bring up
Thread capability In Parallel features
<number>
When to use? Reuse + No stubs and drivers
<number>
Last integration testing step
<number>
UAT = User Acceptance Test (End User)
OAT = Operational Acceptance Test (System Administrators)
Alpha = AT @ the company
Beta = AT @ the field
<number>