Running Tests

[xfq]

It would be useful to add some instructions on how to run the tests (like this). I know that the instructions are different for different MiniApp platforms, and most (if not all) platforms won't pass the tests currently, but I still feel it's useful.

[espinr]

I agree @xfq. So far, we don't have automatic mechanisms to run the tests, only to document them.
In Contributing, I've specified how to create new tests and reports, but not how to test explicitly.

My initial approach is that every unit test (one MiniApp per test) must be loaded and tested on every MiniApp user agent by hand, using their specific loading mechanisms. Since they depend on different platforms and super-apps, the way to load them may vary.

[Edit] -> the summary of the testing process:

1. Every miniapp vendor must use the MiniApps generated and documented in the repository (.ma zipped files),
2. Load each of them in their super-app, or OS through the specific MiniApp loader (I suppose they are different)
3. Observe the result (i.e., is the system asking for the location permission?)
4. Annotate it in the reporting document (i.e., pass, fail, N/A).

Of course, ideally, we should automatize the process, like the WPT, but I think with the current (slower) approach we can start right now. During the WG meeting on May 26, Zhou Dan mentioned two interesting frameworks (Weixin's and SmartApp-CTS) as an approach to check MiniApps, but I understand that this common tool for testing would be a kind of validator (that would be really useful).

Please, miniapp vendors, share your thoughts. I'm happy to adapt the methodology and scripts based on your suggestions.