ml5js/ml5-library

[devops] TravisCI tests fail more often than not - Need to simplify testing and mock network requests

Open

#637 建立於 2019年10月16日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)JavaScript (6,136 star) (905 fork)batch import
bugdevopshelp wantedhigh priority

描述

Dear ml5 community,

I'm submitting a new issue. Please see the details below.

→ Step 1: Describe the issue 📝

Did you find a bug? Want to suggest an idea for feature?

  • Want to suggest an idea

Currently the TravisCI tests fail more often than they pass. This has more to do with the fetching of images for analysis, the instantiation of models making big requests to external pretrained models from google or github servers, etc.

It would be wonderful if we can get this under control so that we can also start making a comprehensive set of tests for our features.

貢獻者指南

技術棧
javascript
領域
devopstesting
議題類型
test
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaScript testingTravisCI configurationHTTP mockingml5 basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
First, examine the existing test suite in the repository to identify which tests make external network requests (e.g., fetching images or model files). Look for opportunities to mock these requests using libraries like nock or sinon. Review the TravisCI configuration file (.travis.yml) to understand the current build process. Consider simplifying the tests by using local fixtures or pre downloaded models to avoid network dependencies. Check issue comments for any specific suggestions or prior attempts.