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.

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

Update testing docs #486

Closed
veripoolbot opened this issue Apr 20, 2012 · 1 comment
Closed

Update testing docs #486

veripoolbot opened this issue Apr 20, 2012 · 1 comment
Labels
area: documentation Issue involves documentation resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor

Author Name: Jeremy Bennett (@jeremybennett)
Original Redmine Issue: 486 from https://www.veripool.org
Original Date: 2012-04-20
Original Assignee: Jeremy Bennett (@jeremybennett)

I've updated the BUGS section of the Verilator user guide based on my recent experiences, to help those writing tests for the first time.

I'm not sure I have everything correct, or even whether this level of detail really belongs in the Internals manual.

I've pushed these changes on GitHub. Please pull from https://github.com/jeremybennett/verilator/tree/test-documentation, commit 2f40448f1d6540221f015a6cc1d90faa4ff12b59.

(GitHub really assumes you are pulling between repositories on GitHub. I'm not sure how I should properly structure a pull request to an external repository like Verilator).
@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2012-04-21T17:00:58Z

Committed. Bonus points for writing documentation!

I think I'd like to leave the main documentation to focus on what the average user needs to run, so I left the intro information you added. The other stuff could be either internals or added to the driver script. The driver script seemed a better spot as it's much closer to the relevant source so I put it there.

@veripoolbot veripoolbot added area: documentation Issue involves documentation resolution: fixed Closed; fixed labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: documentation Issue involves documentation resolution: fixed Closed; fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@veripoolbot