Testing0 - Testing introduction We are typically used to...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Testing introduction We are typically used to thinking of System and tester Using first model in accompanying figure First we design The system then We design the tester Then we use the tester to test the system Consider reversing the roles to that reflected in second model The system is supplying signals to the tester The tester is supplying signals to the system There is really little difference between the two In fact it’s almost like a quiz game Tester supplies signal System answers Question now arises: was the answer correct If yes Proceed down one path If no Down which path to proceed The associated process Fault isolation Debugging As we’ve learned when we design the system Begin at high level of abstraction With functional view Refine that view In increasing levels of detail Until we have sufficient information To implement the design When we design the tester We utilize much same thought and approach process As the design of the system - 1 of 32 - Prior to launching into design of tester Let’s think about what we are trying to do Reflect on what our goals are Look at the test process A Walk Through the Test Process – An Overview Testing can begin during any stage of design process However goals are different at each stage Begin with coarse grained view of test Focus for the moment on test on the design side Stages of Test During early stages Testing for ourselves Key point at this stage We have a design that has never worked We are trying to verify basic Architecture Functionality During these stages Begin with design that is incomplete Over time Design and model larger and larger portions (modules) of the system Confirm that each modeled module or collection of modules Meets required high level specifications Still concerned about real world constraints For low-level internal timing Asynchronous interfaces with outside world Initial focus on Basic functionality Portions of intermodule exchange As design of individual modules and basic integration progresses Focus shifts to low-level details At the module level System level concerns defrayed until later Not time for system level low-level details - 2 of 32 - During middle stages Testing focus remains primarily directed towards Evolving yet incomplete design Presumably by the middle phases Major and minor specification issues have been resolved Larger subsystems being integrated Subsystem level functionality being confirmed During later stages Testing focus remains primarily directed towards Proving system level aspects of design Presumably by the later phases Design issues have been resolved Larger subsystems being integrated System level functionality being confirmed Includes meeting constraints Temporal Behavioural Major difference between Design of system and design of test of the system Design of system Should be top down process Focus first on high level then on details Design of test of system Should be bottom up Focus first on details then on high level A Simple Strategy Approach to testing at all levels...
View Full Document

Page1 / 32

Testing0 - Testing introduction We are typically used to...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online