Initializing LTI key and secret using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti.yml Initializing LTI XML config using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti_xml.yml Initializing LTI key and secret using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti.yml Initializing LTI XML config using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti_xml.yml Initializing LTI key and secret using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti.yml Initializing LTI XML config using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti_xml.yml  (1.7ms) CREATE TABLE "schema_migrations" ("version" varchar NOT NULL)   (0.4ms) select sqlite_version(*)  (0.8ms) CREATE UNIQUE INDEX "unique_schema_migrations" ON "schema_migrations" ("version") ActiveRecord::SchemaMigration Load (0.1ms) SELECT "schema_migrations".* FROM "schema_migrations" Migrating to CreateLtiProviderLaunches (20130319050206)  (0.1ms) begin transaction DEPRECATION WARNING: `#timestamps` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/ngupta/Documents/lti_provider_engine/spec/dummy/db/migrate/20130319050206_create_lti_provider_launches.lti_provider.rb:9)  (0.3ms) CREATE TABLE "lti_provider_launches" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, "canvas_url" varchar, "nonce" varchar, "provider_params" text, "created_at" datetime, "updated_at" datetime) SQL (0.1ms) INSERT INTO "schema_migrations" ("version") VALUES (?) [["version", "20130319050206"]]  (0.8ms) commit transaction ActiveRecord::SchemaMigration Load (0.0ms) SELECT "schema_migrations".* FROM "schema_migrations" Initializing LTI key and secret using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti.yml Initializing LTI XML config using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti_xml.yml ActiveRecord::SchemaMigration Load (0.1ms) SELECT "schema_migrations".* FROM "schema_migrations" ActiveRecord::SchemaMigration Load (0.0ms) SELECT "schema_migrations".* FROM "schema_migrations" Initializing LTI key and secret using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti.yml Initializing LTI XML config using configuration in /Users/ngupta/Documents/lti_provider_engine/spec/dummy/config/lti_xml.yml ActiveRecord::SchemaMigration Load (0.1ms) SELECT "schema_migrations".* FROM "schema_migrations" Migrating to CreateLtiProviderLaunches (20130319050003)  (0.1ms) begin transaction DEPRECATION WARNING: `#timestamps` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in change at /Users/ngupta/Documents/lti_provider_engine/db/migrate/20130319050003_create_lti_provider_launches.rb:8)  (1.3ms) DROP TABLE "lti_provider_launches"  (0.1ms) CREATE TABLE "lti_provider_launches" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, "canvas_url" varchar, "nonce" varchar, "provider_params" text, "created_at" datetime, "updated_at" datetime) SQL (0.1ms) INSERT INTO "schema_migrations" ("version") VALUES (?) [["version", "20130319050003"]]  (0.8ms) commit transaction ActiveRecord::SchemaMigration Load (0.0ms) SELECT "schema_migrations".* FROM "schema_migrations"