Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Action Plan before 09/21/2022 #180

Closed
1 of 9 tasks
tylergu opened this issue Sep 15, 2022 · 1 comment
Closed
1 of 9 tasks

Action Plan before 09/21/2022 #180

tylergu opened this issue Sep 15, 2022 · 1 comment
Assignees
@Essoz @tylergu @unw9527 @taham0

Comments

@tylergu
Copy link
Member

tylergu commented Sep 15, 2022 •
edited by unw9527
Loading

@tylergu

  • Update alarm sheets to map each alarm to bug ID
  • Categorize bugs
  • Compare Acto to existing practices
    • Existing unittests
    • Search for branch coverage, mutation test, test generation tool

@Essoz

  • Update alarm sheets to map each alarm to bug ID

@unw9527

@taham0

  • Update alarm sheets to map each alarm to bug ID
@tylergu
Copy link
Member Author

tylergu commented Sep 15, 2022

@Essoz @unw9527 @taham0 , the immediate action we should do is to update the alarm sheet with unique bug IDs for true alarms. For the true alarms that we reported to the developers, we just use the issue ID. There are some true alarms which we did not report, we can write internal issues describing these true alarms and then use the internal issue ID for the labelling. Some of the true alarms we did not report might actually be worth it to report to developers after we write them down.

@tylergu tylergu closed this as completed Sep 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Essoz Essoz

@tylergu tylergu

@unw9527 unw9527

@taham0 taham0

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Essoz @tylergu @unw9527 @taham0