How do I test Saved-password applications?

Before you roll out your new Saved-password applications to all the users in your district, we recommend testing a few logins. First, make sure that you are using the Clever Portal with Chrome, Firefox, or Edge and have the Clever browser extension installed. You can find instructions for setting up the Chrome extension here.

Here are a few ways to test out a new Saved-password application: 

Testing unsuccessful logins

First, you'll want to make sure the application works when things go wrong. Log in to your Clever Portal with your district admin account. If you've added your new Saved-password application, you should see it in the Portal already. Click on the app icon and enter the wrong credentials. You should see a page that looks like this:

Testing successful logins

Log in to your Clever Portal with your district admin account. If the Saved-password application has been added to the district account, as a district admin, you should already see the application in the Portal. Click on the app icon and enter the correct credentials for your account in the application. Once you click "Save Login" you should be brought to the application website and successfully logged in.

If you followed the steps above to test incorrect credentials, you can test correct credentials by entering them on the page pictured above and simply pressing "Update & Log In." You should be automatically signed into the application.

Testing functionality for different users

Once you've confirmed that the application works with your credentials, you'll want to ensure that it works for students and teachers as well. For this, you'll need credentials from a student and teacher for both the Clever Portal and for the Saved-password application you're testing.

First, in your Clever dashboard confirm the user is scoped for access to the application via the "Select Users" tab of the application page. Next, log in to the Clever Portal as both a student and a teacher. Submit the credentials for each user, respectively, and click "Save Login."

If the application has different login URLs for each user, make sure to test a few different student and teacher accounts to make sure they all work as expected.

If anything goes wrong... 

If any of the tests above don't go as expected, let us know! We're always looking for ways to improve our Saved-password integrations, so your feedback is very much appreciated. As always, any screenshots you can provide will make the troubleshooting process that much faster.

If everything goes right... 

If the tests above work as expected, we recommend piloting the Saved-password application with a subset of students and teachers before rolling it out to the entire district. Read this article for best practices on piloting Saved-password applications!