You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If they hit this button, the topic will be marked as Resolved isResolved=true.
Description: If the user presses this button that has a value that is 'true' or 'false', those values from the button need to be brought to, and updated in the back-end. Namely this would mean that the topic must be edited, and classified as being resolved. Thus there must be a necessary connection through routing an API endpoint to connect the frontend input to update the backend.
Estimated effort: This would require a high degree of effort, as editing topics with relation to the front-end and back-end has not been done prior in this project. Thus there would have to be time spent understanding pre-existing code related to editing topics, and how API routing can be implemented to achieve the resolving of this issue.
Acceptance criteria: This would be through manual testing, ensuring that the user through pressing the button to update a post to be 'Resolved', the topic attribute for Resolved is updated accordingly. So if it was false prior (Unresolved), it becomes true (Resolved). This can also be accomplished through acceptance criteria using the test oracle of asserting that, after calling the necessary code that induces the routing to take into effect, it must be evident that is resolved is 'false' prior, and then becomes 'true', after routing functionality is achieved.
The text was updated successfully, but these errors were encountered:
If they hit this button, the topic will be marked as Resolved isResolved=true.
Description: If the user presses this button that has a value that is 'true' or 'false', those values from the button need to be brought to, and updated in the back-end. Namely this would mean that the topic must be edited, and classified as being resolved. Thus there must be a necessary connection through routing an API endpoint to connect the frontend input to update the backend.
Estimated effort: This would require a high degree of effort, as editing topics with relation to the front-end and back-end has not been done prior in this project. Thus there would have to be time spent understanding pre-existing code related to editing topics, and how API routing can be implemented to achieve the resolving of this issue.
Dependencies: This depends on issues #68 #64
Acceptance criteria: This would be through manual testing, ensuring that the user through pressing the button to update a post to be 'Resolved', the topic attribute for Resolved is updated accordingly. So if it was false prior (Unresolved), it becomes true (Resolved). This can also be accomplished through acceptance criteria using the test oracle of asserting that, after calling the necessary code that induces the routing to take into effect, it must be evident that is resolved is 'false' prior, and then becomes 'true', after routing functionality is achieved.
The text was updated successfully, but these errors were encountered: