2.0 Native API POC

[sethrosetter]

Some notes per conversation with @borrrden

What do our QE tests cover? Anything involving more than just isolated client

Biggest Question

• What coverage does this give us and is developing an Xplat tool necessary?

Functional, LC = LiteCore, P = Platform (iOS, Android, ...)

• REPLICATION!!!
  • (P) client <-> SG
  • (P) client <-> client
  • (P) SSL (By default)
  • (P) SSL client <-> sync_gateway
  • (P) SSL client <-> client
  • (P) Reachability
  • (P) Auth
• (P) Query end to end
  • (P) Xplat Query API - RQG approach
• Long running tests
  • (P) Potential for memory leaks
• Online / offline
  • (LC) Mock client online / offline
  • (P) Platform network detection
• Bad network
  • (LC) Mock bad network
  • (P) Platform network detection
• (P, LC) Concurrent scenario tests
  • concurrent writes
  • concurrent updates
• (P, LC) Multithreaded tests
  • Need specification
• Testing REST api
• Realworld scenarios
  • ex. Combinations of ops.

Perf

• Client
• (LC) Replication performance
• (P) Hardware dependence, could possibly simulate client network (Consumer Wifi)

How do we do this? Ideal requirements:

• Single test definition
• Can run on all platforms

Questions? Do we need Swift or is testing objC ok?

Approaches?

• .NET (Binding libraries)
  • Already a .NET <-> LiteCore binding
• Javascript (there is an embedded interpreter)
  • Investigate how to do this
• Specific tests for every platform
• python binding for LiteCore

POC

• Take a simple doc add / doc get scenario
  • In .NET with bindings
  • Using Javascript binding approach
  • Try to generate python binding to LC (using SWIG or something similar)

[sethrosetter]

We can reuse @borrrden c# bindings to LiteCore instead of maintaining a different set. One downside is that we would be testing against dynamic library (Android, Java, .NET, Mac) on a platform that would be using a static library (iOS)

[sethrosetter]

Question: What is the value add of only using a static lib for iOS platform?