init project

This commit is contained in:
Jasder
2020-03-09 00:40:16 +08:00
commit 2937b2a94d
6549 changed files with 7215173 additions and 0 deletions

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe AdminController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe BlobController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe BoardsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe CommentsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe CourseGroupsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe CourseModulesController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe CourseSecondCategoriesController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe CourseStagesController, type: :controller do
end

View File

@@ -0,0 +1,141 @@
require 'rails_helper'
# This spec was generated by rspec-rails when you ran the scaffold generator.
# It demonstrates how one might use RSpec to specify the controller code that
# was generated by Rails when you ran the scaffold generator.
#
# It assumes that the implementation code is generated by the rails scaffold
# generator. If you are using any extension libraries to generate different
# controller code, this generated spec may or may not pass.
#
# It only uses APIs available in rails and/or rspec-rails. There are a number
# of tools you can use to make these specs even more expressive, but we're
# sticking to rails and rspec-rails APIs to keep things simple and stable.
#
# Compared to earlier versions of this generator, there is very limited use of
# stubs and message expectations in this spec. Stubs are only used when there
# is no simpler way to get a handle on the object needed for the example.
# Message expectations are only used when there is no simpler way to specify
# that an instance is receiving a specific message.
#
# Also compared to earlier versions of this generator, there are no longer any
# expectations of assigns and templates rendered. These features have been
# removed from Rails core in Rails 5, but can be added back in via the
# `rails-controller-testing` gem.
RSpec.describe CoursesController, type: :controller do
# This should return the minimal set of attributes required to create a valid
# Course. As you add validations to Course, be sure to
# adjust the attributes here as well.
let(:valid_attributes) {
skip("Add a hash of attributes valid for your model")
}
let(:invalid_attributes) {
skip("Add a hash of attributes invalid for your model")
}
# This should return the minimal set of values that should be in the session
# in order to pass any filters (e.g. authentication) defined in
# CoursesController. Be sure to keep this updated too.
let(:valid_session) { {} }
describe "GET #index" do
it "returns a success response" do
Course.create! valid_attributes
get :index, params: {}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #show" do
it "returns a success response" do
course = Course.create! valid_attributes
get :show, params: {id: course.to_param}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #new" do
it "returns a success response" do
get :new, params: {}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #edit" do
it "returns a success response" do
course = Course.create! valid_attributes
get :edit, params: {id: course.to_param}, session: valid_session
expect(response).to be_successful
end
end
describe "POST #create" do
context "with valid params" do
it "creates a new Course" do
expect {
post :create, params: {course: valid_attributes}, session: valid_session
}.to change(Course, :count).by(1)
end
it "redirects to the created course" do
post :create, params: {course: valid_attributes}, session: valid_session
expect(response).to redirect_to(Course.last)
end
end
context "with invalid params" do
it "returns a success response (i.e. to display the 'new' template)" do
post :create, params: {course: invalid_attributes}, session: valid_session
expect(response).to be_successful
end
end
end
describe "PUT #update" do
context "with valid params" do
let(:new_attributes) {
skip("Add a hash of attributes valid for your model")
}
it "updates the requested course" do
course = Course.create! valid_attributes
put :update, params: {id: course.to_param, course: new_attributes}, session: valid_session
course.reload
skip("Add assertions for updated state")
end
it "redirects to the course" do
course = Course.create! valid_attributes
put :update, params: {id: course.to_param, course: valid_attributes}, session: valid_session
expect(response).to redirect_to(course)
end
end
context "with invalid params" do
it "returns a success response (i.e. to display the 'edit' template)" do
course = Course.create! valid_attributes
put :update, params: {id: course.to_param, course: invalid_attributes}, session: valid_session
expect(response).to be_successful
end
end
end
describe "DELETE #destroy" do
it "destroys the requested course" do
course = Course.create! valid_attributes
expect {
delete :destroy, params: {id: course.to_param}, session: valid_session
}.to change(Course, :count).by(-1)
end
it "redirects to the courses list" do
course = Course.create! valid_attributes
delete :destroy, params: {id: course.to_param}, session: valid_session
expect(response).to redirect_to(courses_url)
end
end
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe EduDatasController, type: :controller do
end

View File

@@ -0,0 +1,141 @@
require 'rails_helper'
# This spec was generated by rspec-rails when you ran the scaffold generator.
# It demonstrates how one might use RSpec to specify the controller code that
# was generated by Rails when you ran the scaffold generator.
#
# It assumes that the implementation code is generated by the rails scaffold
# generator. If you are using any extension libraries to generate different
# controller code, this generated spec may or may not pass.
#
# It only uses APIs available in rails and/or rspec-rails. There are a number
# of tools you can use to make these specs even more expressive, but we're
# sticking to rails and rspec-rails APIs to keep things simple and stable.
#
# Compared to earlier versions of this generator, there is very limited use of
# stubs and message expectations in this spec. Stubs are only used when there
# is no simpler way to get a handle on the object needed for the example.
# Message expectations are only used when there is no simpler way to specify
# that an instance is receiving a specific message.
#
# Also compared to earlier versions of this generator, there are no longer any
# expectations of assigns and templates rendered. These features have been
# removed from Rails core in Rails 5, but can be added back in via the
# `rails-controller-testing` gem.
RSpec.describe EduSettingsController, type: :controller do
# This should return the minimal set of attributes required to create a valid
# EduSetting. As you add validations to EduSetting, be sure to
# adjust the attributes here as well.
let(:valid_attributes) {
skip("Add a hash of attributes valid for your model")
}
let(:invalid_attributes) {
skip("Add a hash of attributes invalid for your model")
}
# This should return the minimal set of values that should be in the session
# in order to pass any filters (e.g. authentication) defined in
# EduSettingsController. Be sure to keep this updated too.
let(:valid_session) { {} }
describe "GET #index" do
it "returns a success response" do
EduSetting.create! valid_attributes
get :index, params: {}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #show" do
it "returns a success response" do
edu_setting = EduSetting.create! valid_attributes
get :show, params: {id: edu_setting.to_param}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #new" do
it "returns a success response" do
get :new, params: {}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #edit" do
it "returns a success response" do
edu_setting = EduSetting.create! valid_attributes
get :edit, params: {id: edu_setting.to_param}, session: valid_session
expect(response).to be_successful
end
end
describe "POST #create" do
context "with valid params" do
it "creates a new EduSetting" do
expect {
post :create, params: {edu_setting: valid_attributes}, session: valid_session
}.to change(EduSetting, :count).by(1)
end
it "redirects to the created edu_setting" do
post :create, params: {edu_setting: valid_attributes}, session: valid_session
expect(response).to redirect_to(EduSetting.last)
end
end
context "with invalid params" do
it "returns a success response (i.e. to display the 'new' template)" do
post :create, params: {edu_setting: invalid_attributes}, session: valid_session
expect(response).to be_successful
end
end
end
describe "PUT #update" do
context "with valid params" do
let(:new_attributes) {
skip("Add a hash of attributes valid for your model")
}
it "updates the requested edu_setting" do
edu_setting = EduSetting.create! valid_attributes
put :update, params: {id: edu_setting.to_param, edu_setting: new_attributes}, session: valid_session
edu_setting.reload
skip("Add assertions for updated state")
end
it "redirects to the edu_setting" do
edu_setting = EduSetting.create! valid_attributes
put :update, params: {id: edu_setting.to_param, edu_setting: valid_attributes}, session: valid_session
expect(response).to redirect_to(edu_setting)
end
end
context "with invalid params" do
it "returns a success response (i.e. to display the 'edit' template)" do
edu_setting = EduSetting.create! valid_attributes
put :update, params: {id: edu_setting.to_param, edu_setting: invalid_attributes}, session: valid_session
expect(response).to be_successful
end
end
end
describe "DELETE #destroy" do
it "destroys the requested edu_setting" do
edu_setting = EduSetting.create! valid_attributes
expect {
delete :destroy, params: {id: edu_setting.to_param}, session: valid_session
}.to change(EduSetting, :count).by(-1)
end
it "redirects to the edu_settings list" do
edu_setting = EduSetting.create! valid_attributes
delete :destroy, params: {id: edu_setting.to_param}, session: valid_session
expect(response).to redirect_to(edu_settings_url)
end
end
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe GraduationTasksController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe GraduationTopicsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe GraduationWorksController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe HackUserLastestCodesController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe HacksController, type: :controller do
end

View File

@@ -0,0 +1,12 @@
require 'rails_helper'
RSpec.describe HomeController, type: :controller do
describe "GET #index" do
it "returns http success" do
get :index
expect(response).to have_http_status(:success)
end
end
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe HomeworkBanksController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe HomeworkCommonsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe IssueDependsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe IssueTimesController, type: :controller do
end

View File

@@ -0,0 +1,141 @@
require 'rails_helper'
# This spec was generated by rspec-rails when you ran the scaffold generator.
# It demonstrates how one might use RSpec to specify the controller code that
# was generated by Rails when you ran the scaffold generator.
#
# It assumes that the implementation code is generated by the rails scaffold
# generator. If you are using any extension libraries to generate different
# controller code, this generated spec may or may not pass.
#
# It only uses APIs available in rails and/or rspec-rails. There are a number
# of tools you can use to make these specs even more expressive, but we're
# sticking to rails and rspec-rails APIs to keep things simple and stable.
#
# Compared to earlier versions of this generator, there is very limited use of
# stubs and message expectations in this spec. Stubs are only used when there
# is no simpler way to get a handle on the object needed for the example.
# Message expectations are only used when there is no simpler way to specify
# that an instance is receiving a specific message.
#
# Also compared to earlier versions of this generator, there are no longer any
# expectations of assigns and templates rendered. These features have been
# removed from Rails core in Rails 5, but can be added back in via the
# `rails-controller-testing` gem.
RSpec.describe MemosController, type: :controller do
# This should return the minimal set of attributes required to create a valid
# Memo. As you add validations to Memo, be sure to
# adjust the attributes here as well.
let(:valid_attributes) {
skip("Add a hash of attributes valid for your model")
}
let(:invalid_attributes) {
skip("Add a hash of attributes invalid for your model")
}
# This should return the minimal set of values that should be in the session
# in order to pass any filters (e.g. authentication) defined in
# MemosController. Be sure to keep this updated too.
let(:valid_session) { {} }
describe "GET #index" do
it "returns a success response" do
Memo.create! valid_attributes
get :index, params: {}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #show" do
it "returns a success response" do
memo = Memo.create! valid_attributes
get :show, params: {id: memo.to_param}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #new" do
it "returns a success response" do
get :new, params: {}, session: valid_session
expect(response).to be_successful
end
end
describe "GET #edit" do
it "returns a success response" do
memo = Memo.create! valid_attributes
get :edit, params: {id: memo.to_param}, session: valid_session
expect(response).to be_successful
end
end
describe "POST #create" do
context "with valid params" do
it "creates a new Memo" do
expect {
post :create, params: {memo: valid_attributes}, session: valid_session
}.to change(Memo, :count).by(1)
end
it "redirects to the created memo" do
post :create, params: {memo: valid_attributes}, session: valid_session
expect(response).to redirect_to(Memo.last)
end
end
context "with invalid params" do
it "returns a success response (i.e. to display the 'new' template)" do
post :create, params: {memo: invalid_attributes}, session: valid_session
expect(response).to be_successful
end
end
end
describe "PUT #update" do
context "with valid params" do
let(:new_attributes) {
skip("Add a hash of attributes valid for your model")
}
it "updates the requested memo" do
memo = Memo.create! valid_attributes
put :update, params: {id: memo.to_param, memo: new_attributes}, session: valid_session
memo.reload
skip("Add assertions for updated state")
end
it "redirects to the memo" do
memo = Memo.create! valid_attributes
put :update, params: {id: memo.to_param, memo: valid_attributes}, session: valid_session
expect(response).to redirect_to(memo)
end
end
context "with invalid params" do
it "returns a success response (i.e. to display the 'edit' template)" do
memo = Memo.create! valid_attributes
put :update, params: {id: memo.to_param, memo: invalid_attributes}, session: valid_session
expect(response).to be_successful
end
end
end
describe "DELETE #destroy" do
it "destroys the requested memo" do
memo = Memo.create! valid_attributes
expect {
delete :destroy, params: {id: memo.to_param}, session: valid_session
}.to change(Memo, :count).by(-1)
end
it "redirects to the memos list" do
memo = Memo.create! valid_attributes
delete :destroy, params: {id: memo.to_param}, session: valid_session
expect(response).to redirect_to(memos_url)
end
end
end

View File

@@ -0,0 +1,26 @@
require 'rails_helper'
RSpec.describe MessagesController, type: :controller do
describe "GET #index" do
it "returns http success" do
get :index
expect(response).to have_http_status(:success)
end
end
describe "GET #create" do
it "returns http success" do
get :create
expect(response).to have_http_status(:success)
end
end
describe "GET #show" do
it "returns http success" do
get :show
expect(response).to have_http_status(:success)
end
end
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe PraiseTreadController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe ProjectsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe QuestionBanksController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe RepositoriesController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe SchoolsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe StagesController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe StudentWorksController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe SubjectListsController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe TrustieHacksController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe Users::BanksController, type: :controller do
end

View File

@@ -0,0 +1,5 @@
require 'rails_helper'
RSpec.describe VersionReleasesController, type: :controller do
end