Using components in building software systems is a popular approach in software engineering. Testing component based systems (CBS), however is still a challenging task. Additional problems arise, if the tested CBS is a mobile system. Mobile systems offer more challenges, because their structure is dynamic: Components may be added or removed at any time. Thus, testing is required at run time. In this paper we present criteria that a testing approach of mobile CBS has to satisfy. We investigate to what extent common CBS testing approaches fulfill these criteria: For each approach we explore how the particular test steps (test cases, test inputs and test oracles) are created or generated. Although many approaches introduced in the literature assume that testing is needed only at deployment time, we found many interesting features that can be applied in testing mobile CBS, but no existing approach can be