You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main idea is to make sure that after any changes, that the basic functionality still works. These tests should be as general as possible so that if we change html/js, and even the text wording to an extent, these tests shouldn't fail. We'll be making some big changes to Pterodactyl and this should help prevent too many things from getting broken and merged in, now and in the future. Ideally we'll have more feature and integration tests too, but this should serve us well as a starter.
Challenges:
Websockets: The idea is to use Laravel Dusk to open new browser instances that can emulate websockets well enough to receive and reply demonstrating that any servers are or aren't connected.
Assumptions:
Create initial Admin User with php artisan p:user:make and setup panel using defaults
(eg. mysql for db, redis for cache and session, etc.)
Basic Testing Steps
Go to / and see redirect to Log in
Login with bad credentials and see failure to login
Login with good credentials and see redirect to User Dashboard /
See no servers in dashboard yet
Click on Admin Dashboard /admin and see no redirect or not denied access
Click on Users in navigation then click on Create New
Create new non administrator user and see success
Try to create duplicate user and see failure
Click on Locations in navigation and then click on Create New
Create New Location successfully
Click on Nodes in navigation and then click on Create New
Create New Node successfully
any random name and description
pick previously created location
public visibility
fqdn should be local ip
SSL should be turned off as well as no proxy
Defaults and random numbers for the rest
Create 3 new dummy allocations successfully in the same Node
Go back to /admin/nodes and see the heartbeat is red/failing
Startup another browser/server that has a basic websocket reply
See that the heartbeat changes to green/success
Click on Servers in navigation and then click on Create New
Create 3 New Servers successfully
Server Name and Description is any random string
Server Owners should be the admin for two and the non admin for the last one
Each server should have a different allocation
Everything else can be left to default
Exit Admin Panel and see three servers
Click on the middle server and then click on Users in the navigation
Click on New User and enter the same email as the non admin user (full permissions)
Click on logout and see redirect back to login screen
Login as as the non admin user and see two servers
The text was updated successfully, but these errors were encountered:
Main Usage Integration Test
Goals:
The main idea is to make sure that after any changes, that the basic functionality still works. These tests should be as general as possible so that if we change html/js, and even the text wording to an extent, these tests shouldn't fail. We'll be making some big changes to Pterodactyl and this should help prevent too many things from getting broken and merged in, now and in the future. Ideally we'll have more feature and integration tests too, but this should serve us well as a starter.
Challenges:
Websockets: The idea is to use Laravel Dusk to open new browser instances that can emulate websockets well enough to receive and reply demonstrating that any servers are or aren't connected.
Assumptions:
Create initial Admin User with php artisan p:user:make and setup panel using defaults
(eg. mysql for db, redis for cache and session, etc.)
Basic Testing Steps
any random name and description
pick previously created location
public visibility
fqdn should be local ip
SSL should be turned off as well as no proxy
Defaults and random numbers for the rest
Server Name and Description is any random string
Server Owners should be the admin for two and the non admin for the last one
Each server should have a different allocation
Everything else can be left to default
The text was updated successfully, but these errors were encountered: