Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
2bdb5780
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
2bdb5780
编写于
2月 13, 2018
作者:
R
Rémy Coutable
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Port some RuboCop and doc changes from EE
Signed-off-by:
N
Rémy Coutable
<
remy@rymai.me
>
上级
7f4b14b1
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
33 addition
and
6 deletion
+33
-6
.rubocop.yml
.rubocop.yml
+26
-2
doc/development/ee_features.md
doc/development/ee_features.md
+3
-4
doc/development/testing_guide/testing_levels.md
doc/development/testing_guide/testing_levels.md
+4
-0
未找到文件。
.rubocop.yml
浏览文件 @
2bdb5780
...
...
@@ -10,15 +10,26 @@ AllCops:
Exclude
:
-
'
vendor/**/*'
-
'
node_modules/**/*'
-
'
db/*'
-
'
db/*
*/*
'
-
'
db/fixtures/**/*'
-
'
db/geo
/*'
-
'
ee/db/**
/*'
-
'
tmp/**/*'
-
'
bin/**/*'
-
'
generator_templates/**/*'
-
'
builds/**/*'
CacheRootDirectory
:
tmp
# This cop checks whether some constant value isn't a
# mutable literal (e.g. array or hash).
Style/MutableConstant
:
Enabled
:
true
Exclude
:
-
'
db/migrate/**/*'
-
'
db/post_migrate/**/*'
-
'
ee/db/migrate/**/*'
-
'
ee/db/post_migrate/**/*'
-
'
ee/db/geo/migrate/**/*'
# Gitlab ###################################################################
Gitlab/ModuleWithInstanceVariables
:
...
...
@@ -33,3 +44,16 @@ Gitlab/ModuleWithInstanceVariables:
# We ignore spec helpers because it usually doesn't matter
-
spec/support/**/*.rb
-
features/steps/**/*.rb
GitlabSecurity/PublicSend
:
Enabled
:
true
Exclude
:
-
'
config/**/*'
-
'
db/**/*'
-
'
features/**/*'
-
'
lib/**/*.rake'
-
'
qa/**/*'
-
'
spec/**/*'
-
'
ee/db/**/*'
-
'
ee/lib/**/*.rake'
-
'
ee/spec/**/*'
doc/development/ee_features.md
浏览文件 @
2bdb5780
...
...
@@ -28,9 +28,8 @@ we still need to merge changes from GitLab CE to EE. To help us get there,
we should make sure that we no longer edit CE files in place in order to
implement EE features.
Instead, all EE codes should be put inside the
`ee/`
top-level directory, and
tests should be put inside
`spec/ee/`
. We don't use
`ee/spec`
for now due to
technical limitation. The rest of codes should be as close as to the CE files.
Instead, all EE code should be put inside the
`ee/`
top-level directory. The
rest of the code should be as close to the CE files as possible.
[
single code base
]:
https://gitlab.com/gitlab-org/gitlab-ee/issues/2952#note_41016454
...
...
@@ -318,7 +317,7 @@ When you're testing EE-only features, avoid adding examples to the
existing CE specs. Also do no change existing CE examples, since they
should remain working as-is when EE is running without a license.
Instead place EE specs in the
`
spec/
ee/spec`
folder.
Instead place EE specs in the
`ee/spec`
folder.
## JavaScript code in `assets/javascripts/`
...
...
doc/development/testing_guide/testing_levels.md
浏览文件 @
2bdb5780
...
...
@@ -134,6 +134,10 @@ learn more.
[
GitLab QA
]:
https://gitlab.com/gitlab-org/gitlab-qa
[
part of GitLab Rails
]:
https://gitlab.com/gitlab-org/gitlab-ce/tree/master/qa
## EE-specific tests
EE-specific tests follows the same organization, but under the
`ee/spec`
folder.
## How to test at the correct level?
As many things in life, deciding what to test at each level of testing is a
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录