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

Add end to end testing #17

Open
jaisnan opened this issue Jan 13, 2023 · 4 comments
Open

Add end to end testing #17

jaisnan opened this issue Jan 13, 2023 · 4 comments
Assignees
@jaisnan
Labels
must-have release

Comments

@jaisnan
Copy link
Contributor

jaisnan commented Jan 13, 2023

Requested feature: Development time is impacted by having to manually test the extension under multiple contexts and running the proofs. While automating the entire process and running the proofs is not possible, certain parts of the current test suite can be improved and added to the regression/CI as well.
@jaisnan jaisnan changed the title Improve test Improve testing suite Jan 13, 2023
@jaisnan jaisnan changed the title Improve testing suite Add end to end testing suite May 10, 2023
@jaisnan jaisnan changed the title Add end to end testing suite Add end to end testing May 12, 2023
@jaisnan
Copy link
Contributor Author

jaisnan commented May 12, 2023

I think 1-2 end-to-end tests should cover a lot of code given how connected modules are to each other.

@jaisnan
Copy link
Contributor Author

jaisnan commented May 12, 2023

One potential fix is to use something like selenium-electron to simulate user actions entirely.

@jaisnan jaisnan self-assigned this May 12, 2023
@adpaco-aws adpaco-aws mentioned this issue Aug 16, 2023
Merged
4 tasks
@celinval
Copy link
Contributor

https://code.visualstudio.com/api/working-with-extensions/testing-extension

@celinval celinval mentioned this issue Jan 30, 2025
Merged
4 tasks
@celinval
Copy link
Contributor

Once this is done, we should consider adding a CI job to run end-to-end tests before releasing Kani.

celinval added a commit that referenced this issue Jan 31, 2025
@celinval
Remove visualize since it has been removed in Kani (#143)
25489e8 
### Description of changes: 

Remove the broken option to execute `kani --visualize` since that is no
longer supported.

### Testing:

* How is this change tested? I manually tested the changes. We still
need to add support to end-to-end tests per #17

* Is this a refactor change?

### Checklist
- [ ] Each commit message has a non-empty body, explaining why the
change was made
- [ ] Methods or procedures are documented
- [ ] Regression or unit tests are included, or existing tests cover the
modified code
- [ ] My PR is restricted to a single feature or bugfix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaisnan jaisnan

Labels
must-have release
Projects
Kani Extension Bug Bash
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@celinval @jaisnan