See exercism/automated-tests#23

I was trying to complete the Mixed Juices exercise on Javascript track and the solution I came put with seems to be working fine on VScode but when I try running tests on the website I'm getting the YOUR TESTS TIMED OUT error. My solution was:

1. export function timeToMixJuice(name) {
2.     switch(name) {
3.         case 'Pure Strawberry Joy':
4.             return 0.5;
5.         case 'Energizer':
6.             return 1.5;
7.         case 'Green Garden':
8.             return 1.5;
9.         case 'Tropical Island':
10.             return 3;
11.         case 'All or Nothing':
12.             return 5;
13.         default:
14.             return 2.5;
15.     }
16. }
17. 
18. export function limesToCut(wedgesNeeded, limes) {
19.     var wedgesCut = 0; var i = 0;
20.     do {
21.         switch (limes[i]) {
22.             case 'small':
23.                 wedgesCut += 6;
24.                 break;
25.             case 'medium':
26.                 wedgesCut += 8;
27.                 break;
28.             case 'large':
29.                 wedgesCut += 10;
30.                 break;
31.             default:
32.                 break;
33.         }
34.         i++;
35.     } while(wedgesCut < wedgesNeeded);
36.     return i;
37. }
38. 
39. export function remainingOrders(timeLeft, orders) {
40.     do {
41.         timeLeft -= timeToMixJuice(orders[0]);
42.         orders.splice(0,1);
43.     } while(timeLeft > 0);
44. 
45.     return orders;
46. }

I copy pasted the tests it's used to explain the problem in the instructions:

console.log(timeToMixJuice('Tropical Island'));
console.log(timeToMixJuice('Berries & Lime'));
console.log(limesToCut(25, ['small', 'small', 'large', 'medium', 'small']));
console.log(remainingOrders(5, ['Energizer', 'All or Nothing', 'Green Garden']));

And here's the output I get for running this file on VScode (Which is the same as in the instruction):

3
2.5
4
[ 'Green Garden' ]

If possible, this test runner should be updated to version 3 of the test runner interface specification. In version 3, one additional feature is enabled: the ability to link individual tests to tasks. This allows the website to show which tests belong to which tasks.

The way tests are linked to tasks is via an (optional) task_id field, which is an integer that matches the number of the task as defined in the exercise's instructions.md file (note: the instructions start at index 1).

This is an example of a test in the results.json file:

{
  "name": "Expected oven time in minutes",
  "status": "pass",
  "task_id": 1,
  "test_code": "Assert.Equal(40, Lasagna.ExpectedMinutesInOven());"
}

You are completely free in how to implement this. Some options are:

1. Add metadata to a test that the test runner can then discover while running the tests (e.g. an attribute or annotation)
2. Define a test name/task id mapping (e.g. in the exercise's .meta/config.json file)
3. Any other option you can think of...

Let me know if there are any questions.

Below code is for testing the removeItemAtBottom function in Elyses Enchantments problem. But, It's seems to be not working expectedly. Because, the removeItemAtBottom function returs the stack after removing the bottom element. But, In the test code there is no catching the returned stack. Attached the snapshot of the issue for the reference.

Code issue

const stack = [1, 2, 3];
removeItemAtBottom(stack);
removeItemAtBottom(stack);
const expected = [3];
expect(stack).toStrictEqual(expected);


Code Have tobe :

let stack = [1, 2, 3];
stack = removeItemAtBottom(stack);
stack = removeItemAtBottom(stack);
const expected = [3];
expect(stack).toStrictEqual(expected);


Snapshot for Reference:

https://www.npmjs.com/package/jest-circus

This will be the test-runner by default at some point; and it will break this repository. We can get ahead of the game by checking out what the "damage" will be, and what effort is required to upgrade to this runner. It might give us quite a few things we want, as it allows you to not inject globals, get the test name during beforeEach etc.

There is still an error when I copied a correct answer from another solution.

If possible, this test runner should be updated to version 3 of the test runner interface specification. In version 3, one additional feature is enabled: the ability to link individual tests to tasks. This allows the website to show which tests belong to which tasks.

The way tests are linked to tasks is via an (optional) task_id field, which is an integer that matches the number of the task as defined in the exercise's instructions.md file (note: the instructions start at index 1).

This is an example of a test in the results.json file:

{
  "name": "Expected oven time in minutes",
  "status": "pass",
  "task_id": 1,
  "test_code": "Assert.Equal(40, Lasagna.ExpectedMinutesInOven());"
}

You are completely free in how to implement this. Some options are:

1. Add metadata to a test that the test runner can then discover while running the tests (e.g. an attribute or annotation)
2. Define a test name/task id mapping (e.g. in the exercise's .meta/config.json file)
3. Any other option you can think of...

Let me know if there are any questions.

Same as exercism/v3 exercism/javascript etc.

If I try to run the test runner in Docker using ./run-in-docker.sh leap ../javascript/exercises/practice/leap ../javascript/exercises/practice/leap (which assumes there is a sibling javascript repo checked out), I get an error:

Using reporter : /opt/test-runner/dist/reporter.js
Using test-root: /solution/
Using base-root: /opt/test-runner
Using setup-env: /opt/test-runner/dist/jest/setup.js
Using /solution/.meta/config.json as base configuration
Enabling tests in /solution/leap.spec.js
sed: couldn't open temporary file /solution/sedXo2Ajt: Permission denied
sed: couldn't open temporary file /solution/sedaMcAZw: Permission denied
sed: couldn't open temporary file /solution/sedNuro8w: Permission denied

This transformation is done in prepare.sh. If I run ls -al in prepare.sh to check the permissions, I get:

drwxr-xr-x 4 node node 4096 May 12 11:45 .
drwxr-xr-x 1 root root 4096 May 12 11:48 ..
drwxr-xr-x 2 node node 4096 May 12 11:45 .docs
-rw-r--r-- 1 node node  318 May 12 11:45 .eslintrc
drwxr-xr-x 2 node node 4096 May 12 11:45 .meta
-rw-r--r-- 1 node node   12 May 12 11:45 .npmrc
-rw-r--r-- 1 node node 1065 May 12 11:45 LICENSE
-rw-r--r-- 1 node node  252 May 12 11:45 babel.config.js
-rw-r--r-- 1 node node  248 May 12 11:45 leap.js
-rw-r--r-- 1 node node 1107 May 12 11:45 leap.spec.js
-rw-r--r-- 1 node node  816 May 12 11:45 package.json

The Dockerfile specifies that the image is run as user appuser, which then doesn't have the required permissions.

That way someone can easily "test" the test runner without needing any external dependencies?

As stated here, the the solution folder argument has a trailing slash:
exercism/automated-tests@4530211#diff-764565a37bd5e1dd0f2c157d911ec483L10

In line with our new org-wide policy, the master branch of this repo will be renamed to main. All open PRs will be automatically repointed.

GitHub will show you a notification about this when you look at this repo after renaming:

In case it doesn't, this is the command it suggests:

git branch -m master main
git fetch origin
git branch -u origin/main main

You may like to update the primary branch on your forks too, which you can do under Settings->Branches and clicking the pencil icon on the right-hand-side under Default Branch:

We will post a comment below when this is done. We expect it to happen within the next 12 hours.