Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A Android-IMSI-Catcher-Detector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CellularPrivacy
  • Android-IMSI-Catcher-Detector
  • Issues
  • #173
Closed
Open
Issue created Nov 03, 2014 by Administrator@rootContributor

Developer: App Test Protocol

Created by: E3V3A

We need to invent and post a test protocol that can go through a few different situations, that we can detect. The test protocol is meant to be used only for developers and testers to test various features of the app. When app is in beta stage, this test protocol should be extended to test more aspects in a real IMSI-catcher environment.

Basic Tests __________

  • Phone/SIM Information: a) Are all items populated / shown? b) Are the items correct? c) Do the items update immediately when phone changes network or data state?
  • Cell Information: a) Does the current AIMSICD status show? b) Is it correct? ?? c) Are the neighboring cells shown? d) Do they look correct? (Compare with those shown in Service/Engineering Mode.) e) Is Ciphering Information shown?
  • Monitoring Modes: a) Does toggling of Monitoring Mode work as expected? b) Does toggling of 2G lock-in mode work as expected? c) Does toggling of GPS use work as expected? (Maybe this need to be removed?)
  • Antenna Map Viewer: a) Does all BTS show? b) Are they color coded correctly? c) Can you Zoom In/Out? d) Does new BTS pins re-populate the map after (c). e) Does all details of the BTS's show?
  • Database Viewer: a) Does all Databases get properly populated? [See list in #215 (closed).] b) Are all the DB items (as shown) correct? (I.e. LAC, CID, RSSI, etc.)
  • OCID API key: a) Does the API key download work? b) Does the API key entry work? c) Does the API key dispaly work? d) Does the Download OCID data work with the private API key you added in (c)?
  • AT Command Interface: a) Does the AT command interface appear as it should? Compare to this screenshot. b) Does the correct /dev/XXX device (for your phone) appear in the drop-down list? c) Does sending AT in the text box, result in a OK response? d) Does sending ATI in the text box, result in a response with your device info? e) Does sending at+cops? in the text box, result in any response? See this list for others. f) After closing and re-opening ATCoP interface, does it still work the same?
  • Cell Information:
  • Preferences: a) Does the AIMSICD DataBase backup and restore functions work? b) Does the DB table(s) CSV import/export work as expected? c) Does the Automatic AIMSICD Service Start-up on phone boot-up toggle, behave as expected? d) Does the Persistent Service toggle, behave behave as expected? e) Does the FemtoCell Detection behave as it should? f) Does the FemtoCell Protection behave as it should?

Detection Testing ________________

We can test some detections by manually adding some rows to the DBi_measure and DBi_bts tables, and possibly others. We've also started to implement some code to do this, in the test directory. Here are a few items we would like to test.

  • Changing LAC here
  • Changing CID
  • DBe_import inconsistency
  • Silent SMS ...

NOTE: The items above does not yet reflect what is currently present on the Application. We're slowly working on this, since we're still updating the UI/UX.

[More TBA]

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Assignee
Assign to
Time tracking