MENU
Developers at Universal Containers (UC) use version control to share their code changes, but they notice that when they deploy their code to different environments they often have failures. They decide to set up Continuous Integration (CI).
What should the UC development team use to automatically run tests as part of their CI process?
Suggested Answer: A
Get Premium Plat-Dev-201 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Why Salesforce CLI?
The Salesforce CLI supports scripting for Continuous Integration (CI) pipelines, allowing automatic testing and deployment as part of the CI process.
Why Not Other Options?
B: Visual Studio Code is a development IDE, not a CI tool.
C: Force.com Toolkit is outdated and does not support CI processes.
D: Developer Console is for debugging and manual testing, not automation.
31 comments · newest first
RO
Rory
23 days ago
Developer Console is too manual for CI. Not a good choice.
TH
Thaddeus
28 days ago
I agree with Leoma. Salesforce CLI can run tests automatically.
ON
Ona
1 month ago
Visual Studio Code is great, but it’s not automated for tests.
LE
Leoma
1 month ago
I think they should use Salesforce CLI. It integrates well with CI.
GL
Glendora
1 month ago
Developer Console is too manual. Salesforce CLI is the way to go!
JA
Jaleesa
2 months ago
Force.com Toolkit could work, but it's not the best choice for CI.
BE
Bette
2 months ago
Visual Studio Code is great, but it’s not for automation.
RO
Royce
2 months ago
I think they should use Salesforce CLI. It integrates well with CI.
AL
Alesia
2 months ago
Developer Console is too manual for CI. It won't help with automation.
CH
Chau
2 months ago
I agree, Salesforce CLI is the best choice for running tests automatically.
JO
Jose
2 months ago
Visual Studio Code is great, but it’s not for automation.
TO
Tora
3 months ago
I think they should use Salesforce CLI. It integrates well with CI.
BE
Bev
3 months ago
Totally surprised they didn't mention Salesforce DX!
VA
Valentin
3 months ago
Wait, can Developer Console really handle automated tests?
KA
Kayleigh
3 months ago
Force.com Toolkit? I don't think that's meant for CI.
MA
Marjory
3 months ago
I disagree, Visual Studio Code has great integration too.
DU
Dulce
4 months ago
A) Salesforce CLI is the way to go for CI!
EL
Eliseo
4 months ago
Totally surprised they didn't mention Salesforce DX!
SH
Sherita
4 months ago
Wait, can Developer Console really handle automated tests?
JO
Josefa
5 months ago
Force.com Toolkit? I don't think that's meant for CI.
RA
Raul
6 months ago
I disagree, Visual Studio Code has great integration too.
JU
Julio
6 months ago
A) Salesforce CLI is the way to go for CI!
LE
Lemuel
6 months ago
Yeah, CI needs automated testing, Salesforce CLI fits perfectly!
SH
Shawna
6 months ago
Wait, Force.com Toolkit? I didn't think that was for testing at all!
LA
Lavina
6 months ago
I thought Developer Console was more for debugging, not CI.
YA
Yaeko
6 months ago
I disagree, Visual Studio Code has great integration too!
BE
Bette
7 months ago
A) Salesforce CLI is the best choice for CI.
UL
Ulysses
7 months ago
I’m leaning towards the Salesforce CLI too, but I wonder if the Force.com Toolkit could have some testing capabilities as well.
AD
Adaline
7 months ago
The Developer Console seems more like a debugging tool, so I doubt it would be used for CI testing.
JO
Joesph
7 months ago
I remember practicing a similar question, and I think Visual Studio Code is more for development rather than running tests automatically.
IS
Isadora
7 months ago
I think the Salesforce CLI might be the right choice since it can automate tasks and run tests during CI, but I'm not entirely sure.