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

text (template) is not reevaluated after grading #248

Closed
nimdanor opened this issue Apr 16, 2019 · 6 comments
Closed

text (template) is not reevaluated after grading #248

nimdanor opened this issue Apr 16, 2019 · 6 comments
Assignees
Labels
Bug Something isn't working Critical priority This task is very important.

Comments

@nimdanor
Copy link
Member

La balise Text n'est pas réévalué après le passage du grader.
This should be check with a automatique TEST !!!!

I asked for a functionnal test last YEAR.

Properties like this one is a NECESSITY with out reevaluation a lot of exercices are impossible .

so
we need a TEST @Pavell94000
a debug Version @mciissee
an installation !! @qcoumes

@nimdanor nimdanor added the Bug Something isn't working label Apr 16, 2019
@nimdanor nimdanor added the Critical priority This task is very important. label Apr 16, 2019
@nimdanor nimdanor pinned this issue Apr 16, 2019
@mciissee
Copy link
Collaborator

linked to #239 and fixed on fix-239 branch

@nborie
Copy link
Collaborator

nborie commented Apr 16, 2019

IMO, this may be related to #130 ...

@qcoumes qcoumes unpinned this issue Apr 16, 2019
@nimdanor
Copy link
Member Author

nimdanor commented Apr 17, 2019

we need a TEST @Pavell94000
this MUST not pass the release mecanism

@Pavell94000
Copy link
Collaborator

It's a work in progress on the 177_splinter_test branch, but we had a lot of work the last 2 weeks with the 0.6 release

@nimdanor
Copy link
Member Author

ok it's a first priority all the time
WE MUST BE ABLE TO MAKE A SAFE RELEASE
The release rules must be updates with a set of manual tests.

  1. creation of a branch called RC (release candidate) with a number 0.X.Y for the time beeing so next one if RC0.6.0
  2. the push rules of master must be applied to push to RC, i.e. two review
  3. The RC must be deploied on plpreprod.
    Manual tests in lib/tests/manual/ must be done:
  • all pl tests (running pls)
  • all pltp tests (running pltp)
  • all activities tests (running activities)
  • all editor tests (checking the
  • all moodle tests
    If everything pass then the RC is push on the master
  1. The master is pushed on the production.

@nimdanor
Copy link
Member Author

I hope the exams are gooing smooovely :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Critical priority This task is very important.
Projects
None yet
Development

No branches or pull requests

5 participants