| When | Then |
|---|---|
| I start the application | I am presented with the following options: view all departments, view all roles, view all employees, add a department, add a role, add an employee, and update an employee role |
| I choose to view all departments | I am presented with a formatted table showing department names and department ids |
| I choose to view all roles | I am presented with the job title, role id, the department that role belongs to, and the salary for that role |
| I choose to view all employees | I am presented with a formatted table showing employee data, including employee ids, first names, last names, job titles, departments, salaries, and managers that the employees report to |
| I choose to add a department | I am prompted to enter the name of the department and that department is added to the database |
| I choose to add a role | I am prompted to enter the name, salary, and department for the role and that role is added to the database |
| I choose to add an employee | I am prompted to enter the employee’s first name, last name, role, and manager, and that employee is added to the database |
| I choose to update an employee role | I am prompted to select an employee to update and their new role and this information is updated in the database |
Note If a Challenge assignment submission is marked as “0”, it is considered incomplete and will not count towards your graduation requirements. Examples of incomplete submissions include the following:
- A repository that has no code
- A repository that includes a unique name but nothing else
- A repository that includes only a README file but nothing else
- A repository that only includes starter code
- Your GitHub repository containing your application code.
- A walkthrough video that demonstrates the functionality of the employee tracker must be submitted, and a link to the video should be included in your README file.
- The walkthrough video must show all of the technical acceptance criteria being met.
- The walkthrough video must demonstrate how a user would invoke the application from the command line.
- The walkthrough video must demonstrate a functional menu with the options outlined in the acceptance criteria.
- Satisfies all of the preceding acceptance criteria plus the following:
- Uses the Inquirer package.
- Uses the MySQL2 package to connect to a MySQL database.
- Uses the console.table package to print MySQL rows to the console.
- Follows the table schema outlined in the Challenge instructions.
- Repository has a unique name.
- Repository follows best practices for file structure and naming conventions.]
- Repository follows best practices for class/id naming conventions, indentation, quality comments, etc.
- Repository contains multiple descriptive commit messages.
- Repository contains a high-quality readme with description and a link to a walkthrough video.
- The application user experience is intuitive and easy to navigate.
Bonus - Fulfilling any of the following can add up to 20 points to your grade. Note that the highest grade you can achieve is still 100:
- Application allows users to update employee managers (2 points).
- Application allows users to view employees by manager (2 points).
- Application allows users to view employees by department (2 points).
- Application allows users to delete departments, roles, and employees (2 points for each).
- Application allows users to view the total utilized budget of a department—in other words, the combined salaries of all employees in that department (8 points).