Improvements to User.from_omniauth spec setup

Previously this spec was making use of a `User` model and the
`User#serializable_hash` method. However, I'm pretty sure that was just
a convenience and there is nothing actually tying the attributes
returned from OmniAuth to the `User` model attributes.

I've changed the setup so it uses an explicit `Hash` derived from
observing the attributes that OmniAuth actually provides. This seems
more realistic and I'm hoping it will make it easier to apply an
unrelated fix in a subsequent commit.

I've also changed the assertions to be more explicit and like those
in the specs for `User.from_userinfo` & `User.from_token`.

Author: floehopper

spec/models/user_spec.rb

@@ -151,14 +151,22 @@
   describe '.from_omniauth' do
     subject(:auth_subject) { described_class.from_omniauth(auth) }
 
-    let(:user) { build(:user) }
-    let(:info) { user.serializable_hash(except: :id) }
+    let(:id) { 'f80ba5b2-2eee-457d-9f75-872b5c09be84' }
+    let(:info) do
+      {
+        'id' => id,
+        'email' => '[email protected]',
+        'name' => 'John Doe',
+        'roles' => 'school-student'
+      }
+    end
+    let(:user) { described_class.new(info) }
 
     let(:auth) do
       OmniAuth::AuthHash.new(
         {
           provider: 'rpi',
-          uid: user.id,
+          uid: id,
           extra: {
             raw_info: info
           }
@@ -170,8 +178,16 @@
       expect(auth_subject).to be_a described_class
     end
 
-    it 'sets the user attributes correctly' do
-      expect(auth_subject.serializable_hash).to eq user.serializable_hash
+    it 'returns a user with the correct ID' do
+      expect(auth_subject.id).to eq id
+    end
+
+    it 'returns a user with the correct name' do
+      expect(auth_subject.name).to eq 'John Doe'
+    end
+
+    it 'returns a user with the correct email' do
+      expect(user.email).to eq '[email protected]'
     end
 
     context 'with unusual keys in info' do