Practical Competency

• The test must be taken in the VS Code environment on the Programmers site.

• Not taking the test or scoring 0 will result in automatic disqualification.

• The assignment is graded by an automated grading system.

  • You must use the Chrome browser. Developer Tools can be used.

  • If you do not follow the constraints given in the problem statement, grading may not work correctly.

The navigation bar provides the key functions you will need during the test.

Check the problem statement in the Description tab on the right side of the VS Code window.

View information about the Practical Competency test environment, folder structure, and grading process.

Use this if the screen freezes or an error occurs.Your code will be saved automatically before restarting.

Reset the code to its initial state.Unlike End Test, this can be done multiple times.Once initialized, the previous code cannot be restored.

Run grading based on the code you have written so far.Unlike End Test, this can be used multiple times to check if your solution is correct.You can review detailed grading results for each problem. The most recent result will be applied.

Click this when you are done solving all problems and want to finish the test.Once clicked, the test will be closed.The final grading result from Evaluate will be saved on the server.After ending the test, you cannot retake it.

The basic setup is the same as using VS Code on your local computer.

• To run scripts in the terminal, go to the top menu Terminal → New Terminal, or use the shortcut `Ctrl + ``.

• Creating folders or files, running code, and other tasks work the same way as in your local VS Code environment.

The Scoring Log provides information about the entire grading process.

• When you click the Evaluate button, the environment setup and related logs are displayed here.

• You can toggle the log area by clicking on Scoring Log, and adjust its size by dragging it up or down.

➀ In the navigation bar at the top left of the test screen, click Terminal → New Terminal.

➁ In the terminal, enter the command $ ls.You will see the same structure displayed as in the file tree on the left.

➂ Test takers can check the file 0.test-environment.md inside the problem folder to get information about the test environment.

➃ If you are solving Problem 1, use the $ cd command to move into the Problem1 folder. Run the command $ git branch to check the available language (environment) options.

For example, if you want to take the test in nodejs, enter: $ git switch nodejs

➄ After that, click Refresh (↻) in the file tree on the left.

New files and folders will appear.

This confirms that the environment for the selected language (e.g., nodejs) has been set up.

➅ Test takers open the necessary files, such as index.js, to solve the problem.

All information required for the test is provided in the files 0.test-environment.md and 1.code-writing.md .

➆ If you want to solve Problem 2, move to the parent folder using $ cd ...Then go into the folder of the problem you want to solve.

After that, click Refresh (↻) in the file tree on the left to view the files required for that problem.

• In the example image, we move into Problem2 again using $ cd Problem2.

  As with Problem 1, use $ git branch and $ git switch to select the language environment you will use to solve the problem.

➀ In the navigation bar at the top left of the test screen, click Terminal → New Terminal.

➁ In the terminal, enter $ ls. You will see the same structure displayed as in the file tree on the left.

➂ Test takers can check the file 0.test-environment.md or readme.mdinside the problem folder to get information about the test environment

➃ If you are solving Problem 1, use $ cd to move into the Problem1 folder.

➄ Then open the necessary files, such as script.js, to start solving the problem.

• All information required for the test is provided in the readme.md file.

➅ If you want to solve Problem 2, first move to the parent folder using $ cd .., then go into the folder of the problem you want to solve.

• In the example image, we assume Problem 2, so we move again with $ cd Problem2.

• The Evaluate button is located at the top right of the test environment.

• Select the problem you want to grade, then click Start Evaluation to begin.

• Be careful not to click the Evaluate button multiple times, as this may cause unexpected issues.

• Always wait until the above screen appears before running another evaluation.

• You can check the grading process of your code in real time.

• The scoring results are also displayed here.

• If there are multiple problems, a separate tab is created for each problem.

• Click the End Test button at the top right to finish the test.

• Once ended, you will not be able to reconnect or resume the test.

Practical Competency - Where can I check the Practical Competency problem statement?

You can view the problem statement in the Problem tab on the right side of VS Code.If there are multiple problems, use the problem buttons at the bottom left of the Problem tab or the arrow buttons on the right to switch between statements.

Practical Competency - The Scoring Log stopped updating after I ran code evaluation. What should I do?The evaluation process may take some time. While all problems are evaluated simultaneously, the progress for each problem may differ.Please check if any problems are still being graded and wait a little longer.If the grading still does not proceed, please contact support.

Practical Competency - I’m sure my solution is correct, but the result shows “Fail” instead of “Success.” Why?

There are several possible reasons for failed test cases, including:

• Modifying pre-written code arbitrarily

• Ignoring the required format in the problem and focusing only on output

• Providing an incorrect solution

Practical Competency - Where can I find general information about the Practical Competency test?

Click Help in the navigation bar to view details about the test environment, folder structure, grading process, and more.

Practical Competency - Where can I find information about the test environment setup?

• Backend (BE): Check 0.notice.md in the file tree on the left.

• Frontend (FE): Check readme.md in the file tree on the left. These files contain important notes and instructions on setting up the test environment before solving the problems.