Closed Aishwaryasri15 closed 6 months ago
Due to time constraints, I've conducted manual testing for the TA (Teaching Assistant) account type implementation. The testing procedure involved verifying the visibility and functionality of the TA account type option within the user registration form and authentication process. I ensured that users could successfully register and authenticate as Teaching Assistants without encountering any errors. Additionally, I confirmed that existing account types remained unaffected by the addition of TA accounts. The procedure to do manual testing steps mentioned below.
As a developer, I aimed to expand the usability of our platform within educational environments by introducing support for Teaching Assistant (TA) accounts. This feature allows users to register and authenticate as Teaching Assistants, alongside existing account types like "Student" and "Instructor." By incorporating TA account type support into the authentication controller and user registration form, we ensure seamless recognition and handling of TA accounts throughout the platform.
First clone the project:
git clone https://github.com/UCF-CEN-5016/sde-development-project-acv_trio.git
Once the project is cloned, ensure npm is updated:
npm install
Start the Redis server:
redis-server
Setup NodeBB:
./nodebb setup
Start NodeBB:
./nodebb start
Open the webpage with the URL: http://localhost:4567/
To see the changes related to TA account type support, follow these steps:
Estimated Effort: 15 hours
Acceptance Criteria:
Dependencies:
Test Cases Implementation:
To ensure the robustness and effectiveness of this new feature, a set of comprehensive test cases will be implemented. These test cases will focus on verifying the visibility and functionality of the Teaching Assistant (TA) account type within NodeBB. The following test cases will be executed:
Manual Testing:
Unit Tests:
These test cases will guarantee the reliability and functionality of the TA account type addition within NodeBB, ensuring a smooth user experience for all account types across different scenarios and usage contexts.