Skip to content

Releases: Financial-Times/n-test

Use Node v12

02 Oct 08:56
@andygout andygout
v3.0.0
984ceb6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Use Node v12 
Merge pull request #148 from Financial-Times/use-node-v12

Use Node v12
Assets 2
Loading

v2.0.0

28 Sep 08:34
@andygout andygout
v2.0.0
20f8100
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.0.0
  • Upgrade to Node v14
  • Update commander dependency from ^2.13.1 to ^3.0.0
  • Update inquirer dependency from ^5.0.1 to ^7.0.0
Assets 2
Loading

v1.15.0

09 Aug 08:35
@maxcbc maxcbc
v1.15.0
fc8bd24
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.15.0
  • Reduces likelihood of race condition forming on IE tests.
  • Uses webdriver 5.x
  • Disables MicrosoftEdge
Assets 2
Loading

Disable MicrosoftEdge

07 Aug 14:07
@maxcbc maxcbc
v1.15.0-beta.3
fc8bd24
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Disable MicrosoftEdge Pre-release
Pre-release

Microsoft Edge is broken, disable it for now. See issue #128

Assets 2
Loading

Wait for elements on non-chrome tests if waitUntil !== domcontentloaded

07 Aug 10:37
@maxcbc maxcbc
1.15.0-beta.1
ae1783f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Wait for elements on non-chrome tests if waitUntil !== domcontentloaded Pre-release
Pre-release 
1.15.0-beta.1

Merge pull request #125 from Financial-Times/@maxcbc/add-waitUntil-to…
Assets 2
Loading

Unpin puppeteer

18 Jul 11:07
@sjparkinson sjparkinson
v1.14.0
550e67a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Unpin puppeteer 
v1.14.0

chore (deps): unpin puppeteer
Assets 2
Loading

Unpin puppeteer

01 Jul 12:51
@sjparkinson sjparkinson
v1.14.0-beta.1
550e67a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Unpin puppeteer Pre-release
Pre-release 
v1.14.0-beta.1

chore (deps): unpin puppeteer
Assets 2
Loading

Reinstate Safari again

08 Feb 12:22
@carlesandres carlesandres
v1.13.11
e354a1d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Reinstate Safari again

Browserstack seems to have fixed the problem with SafariWebdriver, so I am bring it back

Assets 2
Loading

Disabling Safari again

08 Feb 11:48
@carlesandres carlesandres
v1.13.10
148bfcb
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Disabling Safari again

n-ui are failing with n-test v1.13.9 but this time because of Firefox. My guess it's due to the number of concurrent browsers running. This should be prove that point.

Assets 2
Loading

Reinstate Safari

08 Feb 10:09
@carlesandres carlesandres
v1.13.9
9fea2a0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Reinstate Safari

I asked Browserstack Support and it looks they had a problem on that 6/02/19:

Abhishek M (BrowserStack Support)
Feb 7, 23:08 IST
Hi Carles,
We were certainly seeing some unexpected behavior of "Browser Start-Up failure" on 6th February on Safari. Having said that, the team has already deployed a constructive fix on 6th February itself.
Could you please execute a few sample tests and share the session ID if you continue to see the exception. Please refer ViewSessionID.png for additional reference.
Regards
Abhishek M

I am following their instructions here as they make sense

Assets 2
Loading