marklogic-samplestack icon indicating copy to clipboard operation
marklogic-samplestack copied to clipboard

Upgrade QA / test infrastructure

Open popzip opened this issue 10 years ago • 6 comments

Revisit versions, platforms, machines for testing for next release:

  • Support Java 1.8?
  • Drop IE9 support?
  • Clean machines?
  • see discrepancies on recommended vs. tested npm/node

// @gghai, @laurelnaiad

popzip avatar Jan 23 '15 23:01 popzip

QA infrastructure (VMs and regression as needed) to be upgraded to test following versions for Samplestack 1.1:

OS RHEL 6.6 Windows 7 64-bit Edition (x64)* Mac 10.8 Mountain Lion

Browsers FF 35 IE 10 (on Windows only) Chrome 39

JVM 1.7-71

Other dependencies - to be updated/locked 2 weeks prior to release, based on developer input (see Readmes for documentation - browser/node) npm node bower gulp (to be updated/locked 2 weeks prior to release)

MarkLogic Products MarkLogic 8.0-1 Java Client 3.0.1 Node Client 1.0.0

popzip avatar Feb 27 '15 01:02 popzip

MAC is upgraded to [email protected] . https://github.com/marklogic/marklogic-samplestack/issues/621#issuecomment-90740169

gghai avatar Apr 07 '15 21:04 gghai

Update the list for record purposes .

QA infrastructure (VMs and regression as needed) to be upgraded to test following versions for Samplestack 1.1:

OS RHEL 6.6 Windows 7 64-bit Edition (x64)* Mac 10.8 Mountain Lion

Browsers FF 34 IE 11 (on Windows only) - VM box comes with per-installed browser IE11 .QA has conducted all the tests on IE11 Chrome 41

JVM 1.7-71

Other dependencies - npm node bower gulp (to be updated/locked 2 weeks prior to release)

MarkLogic Products MarkLogic 8.0-1.1

gghai avatar Apr 14 '15 00:04 gghai

Can you please confirm if everything above is included in readme's .Thanks

gghai avatar Apr 16 '15 16:04 gghai

Do you want me to QA the readmes? I might not be best to QA them since I last modified them. Might be better to have a second set of eyes from the QA staff on this?

laurelnaiad avatar Apr 16 '15 19:04 laurelnaiad

This may not require complete README review. Just ensuring the above entries are present in README is a good enough .

gghai avatar Apr 16 '15 19:04 gghai