Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing for new PhET server #584

Closed
5 tasks done
mattpen opened this issue Apr 28, 2016 · 7 comments
Closed
5 tasks done

Testing for new PhET server #584

mattpen opened this issue Apr 28, 2016 · 7 comments

Comments

@mattpen
Copy link

mattpen commented Apr 28, 2016

@phet-steele - The new server is ready for testing from the QA team. I'll list items here that should take highest priority.

  • Browsing the website in various locales, including RTL languages and alternate fonts, such as zh_TW and ar_SA.
  • Test running and downloading simulations
  • Test downloading and uploading contributions
  • Test translating the website and deploying new website translations
  • Test translating and deploying a translation of an HTML5 sim with rosetta

Please make a note of any console errors or broken links that you find during testing. Here is a list of some other problems that might occur.

  • Mixed-content warning, protocols http and https do not match
  • Page failures due to "too many redirects"
  • Abnormally slow response
  • Missing images or other content

@jbphet @ariel-phet @jonathanolson - Please comment if there is anything else that should be tested with the new server. Do we need testing tasks for the installer-builder and the build-server?

@phet-steele
Copy link

@elisemorgan @BryceAG @brroberts1231 @bryo5363 go here for the website:

https://phet-new.colorado.edu/

The above suggestions are a good place to start, but in the end literally everything on this website needs to be tested, including clicking on every single link. It will be very helpful if everyone has an admin account for the website, so if you don't have one then make one (I can help of course). @mattpen do the accounts need to be made on figaro or phet-server (ox)?

@phet-steele will work with @jbphet for initial translation and installer testing (which isn't quite ready). Once a sound procedure is in place it may be possible to get the entire team's help. Until then, @elisemorgan @BryceAG @brroberts1231 @bryo5363 stick to the first three suggested tests. Good luck!

@mattpen
Copy link
Author

mattpen commented Apr 29, 2016

@phet-steele - Accounts should be created on phet-new. Eventually they will be overwritten when we move the database over when we go live.

@mattpen
Copy link
Author

mattpen commented Apr 29, 2016

We should also test user account creation and modification:

  • Create user accounts and newsletter-only accounts
  • Edit the profiles
  • Change the email addresses
  • Change the passwords

@mattpen
Copy link
Author

mattpen commented Jun 30, 2016

We should test the build-server and rosetta on the new server as well.

@mattpen
Copy link
Author

mattpen commented Jun 30, 2016

I will install rosetta on phet-server-dev for testing, do not test rosetta on phet-server.

@mattpen
Copy link
Author

mattpen commented Jul 13, 2016

@phet-steele - Can you do a quick spot check on https://ox-dev.colorado.edu/ for the testing tasks you've already done on phet-new? Now that the server is up with its own domain name, I should be able to get Rosetta configured soon as well.

@ariel-phet
Copy link

@mattpen said this testing issue may now be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants