找流程的问题，发布流程，转测流程，测试流程，开发流程。
这样改进流程，大家都能甩掉过，也能避免下次再出现。

我们也有硬性要求，必须提两个以上的 idea。也没想到什么好的点子。

转开发原因主要是以下几点：
1.不想做功能测试，觉得功能测试在后期跳槽中不会产生太多的价值
2.觉得自己在测试这条路上后面不知道怎么走，对未来比较迷茫。身边没有比我在测试纯技术的路上走的更远的。
3.个人的目标一直是架构师，而成为架构师必定要对开发比较了解。所以感觉能转开发也是实现目标的途径。
4.正好目前的公司鼓励转岗，也愿意花费成本来培养员工，向抓住这个机会。错过这个机会可能以后也不太会有机会了。

大佬说的很有道理。
我们这边的代码权限是公开的，我前后端代码的权限是都有的。也尝试看过相关代码，看懂单个文件没有问题，但是把整个项目连起来看还没有做相关的尝试。主要其中涉及到很多封装和
自认为学习能力还不错，学习和适应时间我感觉半个月到一个月就够了。
还有就是后期换工作的问题，其他我个人思考的是后面如果卷不过开发，再回来卷测试开发也不失为一个好的选择。有了充足的开发经验，再加上之前的测试经验。继续转岗回来做测试开发，我觉得还是比较有优势的。
而且公司比较稳定，暂时也没有考虑过换工作。最少今年不会考虑换工作，等一年后也积累了一定的开发经验。再找开发或者测试开发工作我觉得都是有一定的优势的。

之前做过类似的框架。但是没想到组件公用这一层。现在自己也会写一些前端以后发现，确实是可以在用例中独立一个组件层出来，正常前端用的也就是那些组件的拼装。
后期可以尝试下，这种新的方式。维护量应该会变小

南京就没听说过沙龙是什么东西。。

口语和听力不行，能大致上看懂英语。这个能达到要求吗

能把前端代码分享下吗。最近也在看 react，准备做这一块的开发，也准备用 antd+react

之前做过 rf 框架，unitest 框架还有 pytest 框架的 Jenkins 集成，都是直接在 jenkins 中输入运行命令，jenkins 会自动根据你的运行结果来判断，然后返回成功或者失败，allure 框架集成进去也能返回结果

测试开发确实不只是，测试和开发，运维能力也必不可少。最近自己也在做运维方面的工作。跟着大佬学到很多

完整的 log

08:56:40 Started by user admin
08:56:40 Running as SYSTEM
08:56:40 Building in workspace /var/lib/jenkins/workspace/t
08:56:40 The recommended git tool is: NONE
08:56:40 using credential d5383b4b-1c43-4cf9-b242-9c0dea274b39
08:56:41 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=10
08:56:41 Fetching changes from the remote Git repository
08:56:41 > /usr/bin/git config remote.origin.url https://bitbucket.honeywell.com/scm/ssrtm/web.git # timeout=10
08:56:41 Fetching upstream changes from https://bitbucket.honeywell.com/scm/ssrtm/web.git
08:56:41 > /usr/bin/git --version # timeout=10
08:56:41 > git --version # 'git version 1.9.1'
08:56:41 using GIT_ASKPASS to set credentials
08:56:41 > /usr/bin/git fetch --tags --progress https://bitbucket.honeywell.com/scm/ssrtm/web.git +refs/heads/:refs/remotes/origin/ # timeout=10
08:57:40 > /usr/bin/git rev-parse origin/develop^{commit} # timeout=10
08:57:40 Checking out Revision 1364ef6bd7acab12193f08dade85fa6a3a9f0138 (origin/develop)
08:57:40 > /usr/bin/git config core.sparsecheckout # timeout=10
08:57:40 > /usr/bin/git checkout -f 1364ef6bd7acab12193f08dade85fa6a3a9f0138 # timeout=10
08:57:42 Commit message: "Pull request #2129: Feature/lee/refine dock seting logic"
08:57:42 > /usr/bin/git rev-list --no-walk 8095d4a2d20efdca1b16e65f5aa1fb5517ff5ad7 # timeout=10
08:57:42 > /usr/bin/git remote # timeout=10
08:57:42 > /usr/bin/git submodule init # timeout=10
08:57:42 > /usr/bin/git submodule sync # timeout=10
08:57:43 > /usr/bin/git config --get remote.origin.url # timeout=10
08:57:43 > /usr/bin/git submodule init # timeout=10
08:57:43 > /usr/bin/git config -f .gitmodules --get-regexp ^{submodule.(.+).url} # timeout=10
08:57:43 > /usr/bin/git config --get submodule.src/framework.url # timeout=10
08:57:43 > /usr/bin/git remote # timeout=10
08:57:43 > /usr/bin/git config --get remote.origin.url # timeout=10
08:57:43 > /usr/bin/git config -f .gitmodules --get submodule.src/framework.path # timeout=10
08:57:43 using GIT_ASKPASS to set credentials
08:57:43 > /usr/bin/git submodule update --init --recursive src/framework # timeout=10
08:57:43 [t] $ /bin/sh -xe /tmp/jenkins8760771604762758088.sh
08:57:43 + npm -v
08:57:46 6.14.11
08:57:46 + sudo npm config set @scuf:registry https://artifactory-na.honeywell.com/artifactory/api/npm/SCUF-10305-stable-npm-local/
09:04:48 + sudo npm install
09:06:49
09:06:49 added 6 packages, and audited 3909 packages in 2m
09:06:50
09:06:50 130 vulnerabilities (13 low, 88 moderate, 29 high)
09:06:50
09:06:50 To address issues that do not require attention, run:
09:06:50 npm audit fix
09:06:50
09:06:50 To address all issues possible (including breaking changes), run:
09:06:50 npm audit fix --force
09:06:50
09:06:50 Some issues need review, and may require choosing
09:06:50 a different dependency.
09:06:50
09:06:50 Run npm audit for details.
09:06:50 + sudo npm run prod
09:06:50
09:06:50 > ssrtm@1.0.0 prod
09:06:50 > node changeFileNames && node copyThemeFile && cross-env UMI_ENV=prod umi build
09:06:50
09:07:29 @umijs/plugin-locale WARNING: antd is not installed, unavailable.
09:07:45 Compiling Webpack
09:08:00 Browserslist: caniuse-lite is outdated. Please run:
09:08:00 npx browserslist@latest --update-db
09:09:33 Webpack: Compiled with some errors in 1.81m
09:09:33 ERROR Failed to compile with 11 errors9:09:33 AM
09:09:33
09:09:33 These dependencies were not found:
09:09:33
09:09:33 * /var/lib/jenkins/workspace/t/src/pages/TrailUser/register in ./src/.umi-production/core/routes.ts
09:09:33 * /var/lib/jenkins/workspace/t/src/pages/User/SetPwd in ./src/.umi-production/core/routes.ts
09:09:33 * @/pages/Home/Widgets/Widgets in ./src/.umi-production/core/routes.ts
09:09:33 * @/pages/Home/Widgets/tiles/weather/weatherUtil in ./src/models/weather.ts
09:09:33 * React in ./src/pages/Home/Equipment/Components/ApplyTemplate/ApplyTemplate.tsx, ./src/pages/Home/Equipment/Components/ChangeDeviceStatus/ChangeDeviceStatus.tsx and 3 others
09:09:33
09:09:33 To install them, you can run: npm install --save /var/lib/jenkins/workspace/t/src/pages/TrailUser/register /var/lib/jenkins/workspace/t/src/pages/User/SetPwd @/pages/Home/Widgets/Widgets @/pages/Home/Widgets/tiles/weather/weatherUtil React
09:09:33
09:09:33
09:09:33 These relative modules were not found:
09:09:33
09:09:33 * ./basicAsssetInfo.less?modules in ./src/pages/Home/Equipment/Equipment/components/BasicAsssetInfo/BasicAsssetInfo.tsx
09:09:33 * ./utils/jsonUtil in ./src/framework/src/index.ts
09:09:33 Child
09:09:33

09:09:33 ERROR in ./src/pages/Home/Equipment/Equipment/components/BasicAsssetInfo/BasicAsssetInfo.tsx
09:09:33 Module not found: Error: Can't resolve './basicAsssetInfo.less?modules' in '/var/lib/jenkins/workspace/t/src/pages/Home/Equipment/Equipment/components/BasicAsssetInfo'
09:09:33 @ ./src/pages/Home/Equipment/Equipment/components/BasicAsssetInfo/BasicAsssetInfo.tsx 11:0-52 248:19-25 250:19-25 252:19-25 254:19-25 258:19-25 266:19-25 268:19-25 279:19-25 281:19-25 284:19-25 292:19-25 294:19-25 304:19-25 306:19-25 308:19-25 311:19-25 319:19-25 321:19-25 324:19-25 332:19-25 334:19-25
09:09:33 @ ./src/pages/Home/Equipment/Equipment/DetailAsset/DetailAsset.tsx
09:09:33 @ ./src/pages/Home/Equipment/EQManagement.tsx
09:09:33 @ ./src/.umi-production/core/routes.ts
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/framework/src/index.ts
09:09:33 Module not found: Error: Can't resolve './utils/jsonUtil' in '/var/lib/jenkins/workspace/t/src/framework/src'
09:09:33 @ ./src/framework/src/index.ts 16:0-44 20:0-25:16
09:09:33 @ ./src/pages/Home/Map/DeviceData/DeviceDetailModal/DeviceDetailModal.js
09:09:33 @ ./src/pages/Home/Map/DeviceData/DeviceData.js
09:09:33 @ ./src/pages/Home/Map/RealTimeMonitor.js
09:09:33 @ ./src/.umi-production/core/routes.ts
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/.umi-production/core/routes.ts
09:09:33 Module not found: Error: Can't resolve '/var/lib/jenkins/workspace/t/src/pages/TrailUser/register' in '/var/lib/jenkins/workspace/t/src/.umi-production/core'
09:09:33 @ ./src/.umi-production/core/routes.ts 484:19-486:72
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/.umi-production/core/routes.ts
09:09:33 Module not found: Error: Can't resolve '/var/lib/jenkins/workspace/t/src/pages/User/SetPwd' in '/var/lib/jenkins/workspace/t/src/.umi-production/core'
09:09:33 @ ./src/.umi-production/core/routes.ts 474:19-476:65
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/.umi-production/core/routes.ts
09:09:33 Module not found: Error: Can't resolve '@/pages/Home/Widgets/Widgets' in '/var/lib/jenkins/workspace/t/src/.umi-production/core'
09:09:33 @ ./src/.umi-production/core/routes.ts 51:19-53:43
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/models/weather.ts
09:09:33 Module not found: Error: Can't resolve '@/pages/Home/Widgets/tiles/weather/weatherUtil' in '/var/lib/jenkins/workspace/t/src/models'
09:09:33 @ ./src/models/weather.ts 4:0-82 236:12-28
09:09:33 @ ./src/.umi-production/plugin-dva/dva.ts
09:09:33 @ ./src/.umi-production/plugin-dva/runtime.tsx
09:09:33 @ ./src/.umi-production/core/pluginRegister.ts
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/pages/Home/Equipment/Components/ApplyTemplate/ApplyTemplate.tsx
09:09:33 Module not found: Error: Can't resolve 'React' in '/var/lib/jenkins/workspace/t/src/pages/Home/Equipment/Components/ApplyTemplate'
09:09:33 @ ./src/pages/Home/Equipment/Components/ApplyTemplate/ApplyTemplate.tsx 5:0-31 61:37-56 61:57-71 61:92-111 63:23-42 69:26-45 86:2-21
09:09:33 @ ./src/pages/Home/Equipment/EquipmentInfo/EQProfile/EQSetting.tsx
09:09:33 @ ./src/pages/Home/Equipment/Docks/DockDetail/DockSettings/DockTreeView/DockTreeView.tsx
09:09:33 @ ./src/pages/Home/Equipment/Template/DockTemplate/DockTemplate.tsx
09:09:33 @ ./src/.umi-production/core/routes.ts
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/pages/Home/Equipment/Components/ChangeDeviceStatus/ChangeDeviceStatus.tsx
09:09:33 Module not found: Error: Can't resolve 'React' in '/var/lib/jenkins/workspace/t/src/pages/Home/Equipment/Components/ChangeDeviceStatus'
09:09:33 @ ./src/pages/Home/Equipment/Components/ChangeDeviceStatus/ChangeDeviceStatus.tsx 5:0-31 66:37-56 66:57-71 66:92-111 68:23-42 74:26-45 91:2-21
09:09:33 @ ./src/pages/Home/Equipment/Docks/DockList.tsx
09:09:33 @ ./src/.umi-production/core/routes.ts
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/pages/Home/Equipment/Components/SetParams/SetParams.tsx
09:09:33 Module not found: Error: Can't resolve 'React' in '/var/lib/jenkins/workspace/t/src/pages/Home/Equipment/Components/SetParams'
09:09:33 @ ./src/pages/Home/Equipment/Components/SetParams/SetParams.tsx 9:0-31 133:36-55 144:35-54 150:38-57 152:22-41 155:40-59 157:22-41 159:23-42 167:30-49 167:50-64 168:26-45 188:2-21
09:09:33 @ ./src/pages/Home/Equipment/Docks/DockList.tsx
09:09:33 @ ./src/.umi-production/core/routes.ts
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/pages/Home/Equipment/Components/SetPassword/SetPassword.tsx
09:09:33 Module not found: Error: Can't resolve 'React' in '/var/lib/jenkins/workspace/t/src/pages/Home/Equipment/Components/SetPassword'
09:09:33 @ ./src/pages/Home/Equipment/Components/SetPassword/SetPassword.tsx 5:0-31 52:26-45 52:76-95 54:22-41 54:83-102 54:145-164 86:26-45 106:2-21
09:09:33 @ ./src/pages/Home/Equipment/Docks/DockList.tsx
09:09:33 @ ./src/.umi-production/core/routes.ts
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33

09:09:33 ERROR in ./src/pages/Home/Organization/Sites/Site/Gateway/Components/ManuallyAssignDock/ManuallyAssignDock.tsx
09:09:33 Module not found: Error: Can't resolve 'React' in '/var/lib/jenkins/workspace/t/src/pages/Home/Organization/Sites/Site/Gateway/Components/ManuallyAssignDock'
09:09:33 @ ./src/pages/Home/Organization/Sites/Site/Gateway/Components/ManuallyAssignDock/ManuallyAssignDock.tsx 9:0-31 285:26-45 287:22-41 289:22-41 291:22-41 293:23-42 304:24-43 306:22-41 308:22-41 310:22-41 317:23-42 324:23-42 331:24-43 336:25-44 338:22-41 349:25-44 351:22-41 363:26-45 365:22-41 370:28-47 382:26-45 443:30-49 443:50-64 444:26-45 444:46-60 444:81-100 466:2-21
09:09:33 @ ./src/pages/Home/Organization/Sites/Site/Gateway/Info/GatewayInfo.tsx
09:09:33 @ ./src/.umi-production/core/routes.ts
09:09:33 @ ./src/.umi-production/umi.ts
09:09:33 @ multi ./src/.umi-production/umi.ts
09:09:33 null
09:09:33 build failed
09:09:33 Error: build failed
09:09:33 at /var/lib/jenkins/workspace/t/node_modules/@umijs/bundler-webpack/lib/index.js:138:27
09:09:33 at finalCallback (/var/lib/jenkins/workspace/t/node_modules/webpack/lib/MultiCompiler.js:254:12)
09:09:33 at /var/lib/jenkins/workspace/t/node_modules/webpack/lib/MultiCompiler.js:277:6
09:09:33 at done (/var/lib/jenkins/workspace/t/node_modules/neo-async/async.js:2931:13)
09:09:33 at runCompilers (/var/lib/jenkins/workspace/t/node_modules/webpack/lib/MultiCompiler.js:181:48)
09:09:33 at /var/lib/jenkins/workspace/t/node_modules/webpack/lib/MultiCompiler.js:188:7
09:09:33 at /var/lib/jenkins/workspace/t/node_modules/webpack/lib/MultiCompiler.js:270:7
09:09:33 at finalCallback (/var/lib/jenkins/workspace/t/node_modules/webpack/lib/Compiler.js:257:39)
09:09:33 at /var/lib/jenkins/workspace/t/node_modules/webpack/lib/Compiler.js:273:13
09:09:33 at AsyncSeriesHook.eval as callAsync
09:09:33 at AsyncSeriesHook.lazyCompileHook (/var/lib/jenkins/workspace/t/node_modules/tapable/lib/Hook.js:154:20)
09:09:33 at onCompiled (/var/lib/jenkins/workspace/t/node_modules/webpack/lib/Compiler.js:271:21)
09:09:33 at /var/lib/jenkins/workspace/t/node_modules/webpack/lib/Compiler.js:681:15
09:09:33 at AsyncSeriesHook.eval as callAsync
09:09:33 at AsyncSeriesHook.lazyCompileHook (/var/lib/jenkins/workspace/t/node_modules/tapable/lib/Hook.js:154:20)
09:09:33 at /var/lib/jenkins/workspace/t/node_modules/webpack/lib/Compiler.js:678:31
09:09:33 Build step 'Execute shell' marked build as failure
09:09:34 Finished: FAILURE

T3 据说在内斗。。进去站不好队就干掉了。真的假的啊

我也是 14 年的。。。毕业回老家找工作找工作没找到合适的。网上看到测试培训，就去了。。出来找工作，第一个就去的华为外包，学了点基础，出来胡吹涨了 30%，然后差不多每年一跳，涨 30%。今年跳槽，差不多涨了 50%。python 和自动化纯自学，进过两次培训班，现在在南京也算是快到测试的天花板了。后面只能看看能不能转到测试架构师了，毕竟个人感觉测试开发这个岗位也不能撑过 35 岁

南京的机会太少了。能招得起你这个级别的没几家，面试一家少一家，确实要谨慎一点。南京的天花板相对也比较低，感觉 20 多 K 的机会都不多了。可能再过两年我也会有你这样的忧愁吧。共勉

我是第一份工作经历是外包的，然后被刷掉了，帮忙内推的人说是因为外包经历，具体就不太清楚了

最终了解了下，准备去的下家公司后端还是以 Java 为主，考虑到目前国内后端开发还是 Java 为主，自身发展也更偏向于后端，对后端更了解一些，选择 Java 做第二门语言，在看 Java 视频的时候，遇到前端部分也会学习下，不会太深入。希望后期自己可以用 Java 做出一些东西，不停留在 hello world 层次

有点难坚持。。最长坚持了两个月，每天刷一题。。后面就没坚持下来了。毅力不够 (/ω＼)

主要公司没什么机会让我用起来。。目前只能自己玩玩，所以导致学习了，但是学的不够深入，丢的也快

槽神说的有道理，但是高深的我都没用上过。。。就写写自动化，写写脚本，做做后端开发。还是太肤浅了

java、js 之前都大致上看过，后来犹豫工作用不上，又遗弃了，感觉捡起来相对还是更简单点。还是很纠结

据说虾皮有外包经历的会直接把简历筛掉？

能说下南京具体在哪里吗，具体是哪家公司

南京确实外包比较多，本地唯一算大厂的苏宁跟外包也差不了多少，其他大厂比较少了。虽说都有分公司，但是招人还是比较少的

有点类似于 UI 自动化的 PO 模式写出来的框架。将各个功能分到了对应的文件里面，直接 UI 自动化跟这个思路差不多，接口也用这个思路写过