1 / 25

Testing a Bluetooth Product With Web and Embedded Software

Testing a Bluetooth Product With Web and Embedded Software. Rick Clements cle @ cypress.com Cypress Semiconductors 9125 SW Gemini Dr., Suite 200 Beaverton, OR 97008. Purpose. Embedded & web based software have different constraints Embedded & web based software have different tools

anisa
Download Presentation

Testing a Bluetooth Product With Web and Embedded Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Testing a Bluetooth Product With Web and Embedded Software Rick Clementscle@cypress.comCypress Semiconductors9125 SW Gemini Dr., Suite 200Beaverton, OR 97008

  2. Purpose • Embedded & web based software have different constraints • Embedded & web based software have different tools • The embedded & web environments are merging • Provide a planning example of a project in both environments

  3. Presentation Structure • The process is in the paper • Sample documents are in the appendix • Slides available at http://www.geocities.com/rick_clements/blue.ppt

  4. Overview • Product under test • Scoping the effort • The QA plan • The test plan • Questions • Summary

  5. Product Under Test Server Bluetooth Local PC Internet Server

  6. Scoping The Effort • Software environments • Organization of the team • Tools

  7. Internet & Windows Compatibility with different servers running different OS Servers may be busy or unavailable Large amount of memory locally, storage locally and storage on servers Tools for testing memory leaks, measuring test coverage and automating tests exist Embedded Runs on a single device Playing music requires real-time limits of msec. A limited memory & storage Few off the shelf tools Scoping The Effort Software Environments

  8. Scoping The Effort Possible Team Organization • Test & QA team per discipline • Software • Electrical • Mechanical • Single combined team • System testing encompasses all disciplines

  9. Scoping The Effort Organization Of The Team • Test lead • Electrical, mechanical & software debug - designers • Embedded software - 1 software test engineer • Windows & web software- 1 software test engineer • Internal mechanical & electrical - 1 mechanical test engineer • EMI & UL tests - 1 environmental test engineer

  10. Scoping The Effort Tools • Windows and Internet - commercial test tool • Embedded test tools developed internally • This is a full development effort • It needs adequate planning, time & resources • Scopes, in circuit emulator, etc. • Time at EMI and UL facilities will be rented

  11. The QA Plan • Configuration management • Software / hardware changes • Typical change • Hardware description languages • Product / web configuration • Issue tracking

  12. QA Plan Typical Change • Requirement for monitoring battery usage discovered • Add a gas gauge chip • Electrical & mechanical change • Add software driver for the chip • Add software to display status on GUI • Configuration management vitally important

  13. QA Plan Hardware Description Languages • Blurs the line between software and Hardware • Source easily managed • Graphical environment - same issues as Windows • Configuration management a “software thing”

  14. QA Plan Product / Web Configuration • Web content changes quickly • Software on PC changes more slowly • Firmware in device changes more slowly • Address in product & tests plans

  15. QA Plan Issue Tracking • It’s a software problem • Investigation shows electrical problem • Fix it in software • Must have a common tracking system

  16. The Test Plan • Tools • Hooks into the product • Reviews • Compatibility tests • Host / device tests • Stress tests • Power tests • Electrical & mechanical tests • Schedule • Schedules & staffing levels - Cem Kaner & Kathy Iberle papers

  17. Test Plan Tools • Web & windows tool selection • Embedded tool development • Buy or rent tools for electrical and mechanical tests

  18. Test Plan Hooks Into The Product • Affect the test approach • Warning and status easier to test • RS232 vs Bluetooth

  19. Test Plan Reviews • Catch error early • High risk • Interfaces • New technology • Tight timing requirements • Extendibility • Multiple languages • Multiple host platforms

  20. Test Plan Compatibility Tests • Product / web servers • Gold, silver & don’t care sites • Test when product OR site changes • On going management • Operating systems • Windows 95?, 98, ME, NT, 2000, XP? • Bluetooth cards in the host

  21. Test Plan Host / Device Tests • Protocol • Standard • Proprietary • Error handling • Handled by hardware • Handled by software

  22. Host Tests Low memory in host Device Tests Play music, change pages & download Automation Commands over Bluetooth Two way communication changes timing Must be manual Test Plan Stress Tests

  23. Test Plan Power Tests • Operates over entire battery life - hardware • Displays accurate battery life - software

  24. Internal Tests Heat Operation LCD readable Drop tests Shipping container Agency Tests EMI UL Test Plan Electrical & Mechanical Tests

  25. Summary • Many different areas • Web software • PC software • Embedded software • Electrical • Mechanical • You can’t be an expert in all areas • You need a good team

More Related