Node.js problem creation [Project Based Back-end]

Created by DoSelect Content Devs, Modified on Mon, 24 Mar at 7:27 PM by DoSelect Content Devs

Given below is the process through which you can create a problem of type: Node.js Project Based Back-end

1. Landing on the Dashboard

When you log in to DoSelect Platform, you arrive at the Home dashboard.
From here, you can manage tests and access the Library tab at the top of the page.
Action: Click on the Library tab to move to the question bank.

2. Navigating to Problem Creation

Once in the Library, you will see available libraries like DoSelect Questions and My Company Questions.
At the bottom-right corner, you will find a + (plus) button.
Action: Click on the + Create a new problem button to start creating your problem.

3. Configuring Basic Problem Details (Required)

A dialog box titled "Create New Problem" will appear.
Fill the following fields:
- Name: Enter a descriptive and concise problem title (e.g., "Node.js: Stocks API"). Try to keep it concise and meaningful, as the title has a 45-character limit.
- Problem Type: Choose Project Based: BackEnd.
- Level: Select difficulty level – Easy, Medium, or Hard.
- Framework: Choose from Node.js (14) or Node.js + MongoDB, based on the requirement.
Action: Click Create to continue.

4. Setting Up the Project

You will land on the Problem Setup Interface.
Choose one of the two setup methods:
- Upload ZIP: Upload a .zip file of the project.
- GitHub Link: Provide a repo link for setup.

Using Upload ZIP Method (Required)

Download the projecttemplate.zip file provided.
Modify it locally as per the problem requirement.
Remove core logic to convert it into a Project Stub.
Compress and upload the stub via the interface.

Project Stub (Required)

This is the version of the project with key logic removed.
Candidates fill in the required logic.
Must be uploaded in .zip format (max 5MB).
Open in Editor option allows you to view/edit the stub in the online editor.

Sanity Check (Required)

Ensures the stub is valid and will run:
- ZIP file < 5MB
- Extracted contents < 20MB
- Proper structure & valid config format.

Project Solution (Required)

Enable this to upload the fully working solution for reference.
Upload the complete version of your modified project (with logic).
Run the Sanity Check to verify everything compiles and works as intended.

5. Filling Remaining Problem Details

Problem Name (Optional)

This section allows you to modify the name provided during initial setup, if needed.

Expected Solving Time (Required)

Indicate how long a candidate should take (e.g., 60, 90, or 120 minutes).
Helps in difficulty tagging and test setup.

Description (Required)

Main problem statement seen by the candidate.
Must include:
- Context
- Task Description
- Requirements
Use formatting tools and preview for clarity.

Difficulty Level (Optional)

This section allows you to modify the level provided during initial setup, if needed.

Scoring (Optional)

Assign points (e.g., 75).
Penalty is not applicable for project-based problems (keep at 0).

Maximum Re-Submissions (Optional)

Set to 0 for unlimited submissions (recommended).

Tags (Optional)

Discovery Tags: These tags are helpful for searching and categorizing problems within your own library.
Insight Tags: Helps in tracking performance and getting key insights on specific problem areas or topics (e.g., JWT, Error Handling).

Attachments (Optional)

Upload related resources like:

6. Finalizing the Problem

Evaluation Details

Summarizes mode and score.
Default for project-based problems is Automated Testing Framework.

Action Buttons

Save Problem: Saves all progress.
Save and Clone: Duplicates the problem.
Lock: Finalizes the problem. No further edits.
Archive Problem: Hides the problem from test usage.
Try This Problem: Simulates candidate view in test mode.
Problem Analytics: Insights on problem attempts, correct submissions, and used in tests.

Note: Ensure all required fields (marked with a red asterisk *) are filled. Otherwise, the problem will remain incomplete and cannot be used in tests.