@@ -70,7 +70,20 @@ exports.config = {
70
70
// and 30 processes will get spawned. The property handles how many capabilities
71
71
// from the same test should run tests.
72
72
//
73
- maxInstances : 6 ,
73
+ // NOTE: The above description of maxInstances from WebdriverIO does not appear to be correct.
74
+ // maxInstances seems to determine how many total browser instances can be open at once.
75
+ // If there are for example 9 test files and 2 capabilities (Firefox and Chrome, say) and
76
+ // maxInstances is set to 9, webdriverio will open 5 Chrome windows and 4 Firefox windows.
77
+ //
78
+ // See this ticket:
79
+ //
80
+ // "Open Square search: Firefox browser tests failing in prod with connection failure errors"
81
+ // https://jira.nyu.edu/jira/browse/NYUP-682
82
+ //
83
+ // ...for reason why Firefox must be limited to a single instance. We therefore
84
+ // set global maxInstances to 7 to allow for 6 Chrome instances, one for each
85
+ // test suite, and one single Firefox instance.
86
+ maxInstances : 7 ,
74
87
//
75
88
// If you have trouble getting all important capabilities together, check out the
76
89
// Sauce Labs platform configurator - a great tool to configure your capabilities:
@@ -98,7 +111,14 @@ exports.config = {
98
111
// maxInstances can get overwritten per capability. So if you have an in-house Selenium
99
112
// grid with only 5 firefox instances available you can make sure that not more than
100
113
// 5 instances get started at a time.
101
- // maxInstances : 5,
114
+
115
+ // See this ticket:
116
+ //
117
+ // "Open Square search: Firefox browser tests failing in prod with connection failure errors"
118
+ // https://jira.nyu.edu/jira/browse/NYUP-682
119
+ //
120
+ // ...for reason why Firefox must be limited to a single instance.
121
+ maxInstances : 1 ,
102
122
//
103
123
browserName : 'firefox' ,
104
124
'moz:firefoxOptions' : {
0 commit comments