-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
@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! |
@phet-steele - Accounts should be created on phet-new. Eventually they will be overwritten when we move the database over when we go live. |
We should also test user account creation and modification:
|
We should test the build-server and rosetta on the new server as well. |
I will install rosetta on phet-server-dev for testing, do not test rosetta on phet-server. |
@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. |
@mattpen said this testing issue may now be closed |
@phet-steele - The new server is ready for testing from the QA team. I'll list items here that should take highest priority.
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.
@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?
The text was updated successfully, but these errors were encountered: