Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ECMA 6 - Constants and variables and Map/Set tests #139

Merged
merged 13 commits into from
Jun 13, 2018

Conversation

pemattio
Copy link
Contributor

@pemattio pemattio commented May 21, 2018

Work for the following issues:

#132 and #118

@Undre4m
Copy link
Collaborator

Undre4m commented May 21, 2018

Hey, thanks for the PR!

I see you are fixing the indentation errors... You can run grunt travis if you want to run the static code analysis and the tests locally.

As a general rule, you should add an assert.equal(result.success, true); or similar on every test to check if execution didn't fail. Sometimes the runtime breaks while running the test but returns the expected result anyway.

As for the tests i didn't examine them closely but they look good to me!

@@ -0,0 +1,59 @@
// Copyright (c) 2013 - present UTN-LIS
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review indentation. Please take note of unsupported cases for Puma. This will help to define future tasks on the runtime support.

define(['pumascript'], function (puma) {

QUnit.module("Ecma6-Map-Set-And-WeakMap-WeakSet-Tests");
skip("Map get method", function(assert) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leave empty blank line

assert.equal(result.value, true);
});

skip("Variable let block scope", function(assert) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multiple variable asignation.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emravera emravera changed the title First ECMAScript 6 tests #132 First ECMAScript 6 tests May 21, 2018
@emravera emravera changed the title #132 First ECMAScript 6 tests First ECMAScript 6 tests May 21, 2018
var result = puma.evalPuma("let s = new Set(); s.add('hello').add('goodbye').add('hello'); s.size === 2;");
assert.equal(result.value, true);
});
});
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add empty line at the end.

@emravera
Copy link
Collaborator

Really good job! Just small comments!

@pemattio pemattio changed the title First ECMAScript 6 tests ECMA 6 - Constants and variables and Map/Set tests May 28, 2018
assert.ok(result.success && result.value === 'undefined');
});

});
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add blank line at EOF

Copy link
Collaborator

@emravera emravera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Add the empty blank line at EOF.

@Undre4m Undre4m merged commit 0b1deb6 into pumascript:master Jun 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants