globalizejs/globalize

Tests: Dependencies

Open

#372 建立於 2014年12月19日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)JavaScript (4,759 star) (645 fork)batch import
help wanted

描述

On https://github.com/jquery/globalize/pull/370, we had missing dependencies. But, we were unable to figure that out by our current unit tests. They are indirect dependencies (i.e., "plugin dependencies") and another parallel unit test was loading them before they were being used. Therefore, no problem occurred until we started to test them on high latency envs like via browserstack-runner.

Ideally, each unit test should be executed using the dependencies it's explicitly requiring with no interference.

貢獻者指南

技術棧
javascript
領域
testing
議題類型
test
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
JavaScriptunit testingglobalize library
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Review the linked PR #370 to understand the missing dependencies issue. Examine the current test setup in globalize to identify where each test file loads its dependencies. Look for patterns where parallel tests inadvertently load dependencies for others, and design a per test dependency injection approach. The goal is to ensure each unit test explicitly requires its own dependencies without interference from other tests.
Tests: Dependencies · globalizejs/globalize#372 | Good First Issue