Abstract
Testing a component in embedded devices encompasses - testing it as stand-alone in terms of its APIs and testing it in the context of its seamless integration into the embedded environment. Such testing needs to aim at bringing out domain and component specific issues to be effective. This paper describes how we handled testing of one such component viz. predictive text software in Mobile devices, the idea being to share the lessons learned, challenges faced and the aspects missed. Part of this, the paper explores the road we as a test team traveled in the project initial stages and describes how it led to effective testing. In addition, the paper talks about how we built reuse into the test environment for the component.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
