artlee06 / pe Goto Github PK

Although the intention is after finalising, these attributes cannot be edited, a user might accidentally key in finalise prematurely. After having an interview with one person he might think of more attributes or metrics he wants to measure but there is no way to add the metric to the same session afterwards.

I would suggest that instead of a finalise command, it should be made into a lock command to lock the current metrics and attributes and questions in before an interview. Afterwards, the user could key in an unlock command to edit again. Granted it would be unfair to the interviewees to have different attributes and questions but that is up to the interviewer to discern for himself. The option for the interviewer to edit after a finalise should at least be there.

The resume can be uploaded and when you upload it will be replaced by the latest upload which is good. However there is no clear command for me to delete the resume after uploading without deleting the person from the database entirely.

In the UG, the export command is export <interviewee>.

In the DG, the export command in manual testing is report <interviewee>

Could it be the fact that I do not have any attributes or metrics for the interviewee?

Steps to reproduce:

1. Upload resume for Bob
2. Prepare some questions for Bob
3. finalize
4. Interview Bob and add some remarks
5. End the interview
6. open Bob
7. close report
8. report Bob

Unknown command after report Bob

Reference for what Bob has after the interview

The prerequisite for F4 requires me to have an interviewee Jane with alias Doe. As as someone who is testing based on knowledge from the manual testing section alone from F1 to F3, I had to experiment myself on how to edit the alias and achieve the prerequisite for F4.

The grammar here is a bit awkward : "During review process before the commencement of interviews,". Perhaps change it to " During review process and before the commencement of interviews,"