[Koha-bugs] [Bug 34076] [ALTERNATE] [DOCS] Automated screenshots using Cypress.io testing framework

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34076

--- Comment #21 from Caroline Cyr La Rose <caroline.cyr-la-rose at inlibro.com> ---
(In reply to Jonathan Druart from comment #20)
> (In reply to Caroline Cyr La Rose from comment #17)
> >  In step 6 still, the first commit command didn't work for me, I think
> > because the file did not exist before (nothing added to commit but untracked
> > files present (use "git add" to track)), so I did
> > 
> >     git add 4-library.ts
> > 
> >     git commit -m "auto librarylist"
> 
> Correct, good catch! I am not sure what's the best solution to adjust the
> test plan... :-/

I think this command in two steps would always work, whether the file already
exists or not (it's the way I always do it...). I know developers prefer
shorthand versions ;) but this would work universally. Git "experts" would know
to use the shorthand and wouldn't have to follow step by step each command. If
the test plan is aimed at non developers and the purpose is to give us an easy
step by step to follow, I would say to write it as two commands.

I was only mentioning it in case a git novice stumbled upon it and was stuck
there. As you know, I'm often stuck when commands don't behave exactly as
they're supposed to :)

Maybe you don't have to change the test plan right away and keep it in your
back pocket for when writing the actual how-to?

-- 
You are receiving this mail because:
You are watching all bug changes.