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

Chapter "Testing Data Storage" in the wrong location. #44

Closed
clviper opened this issue Dec 13, 2016 · 4 comments
Closed

Chapter "Testing Data Storage" in the wrong location. #44

clviper opened this issue Dec 13, 2016 · 4 comments

Comments

@clviper
Copy link
Collaborator

clviper commented Dec 13, 2016

This chapter is located in /Document/Testcases/0x00_OMTG-DATAST.md From what I understood it should be placed in the root of the /Document folder.

@clviper
Copy link
Collaborator Author

clviper commented Dec 13, 2016

And the name itself should be rename to the right format.

@sushi2k
Copy link
Collaborator

sushi2k commented Dec 14, 2016

Hi clviper,

can you please elaborate what you mean that it is in the wrong location? This repo is not really for reading the final document, at the moment you can create a docx or html out of the markdown by a shell script (https://github.com/OWASP/owasp-mstg/blob/master/generate_document.sh). This will be the deliverable.

We were also already thinking about merging to Gitbooks, to make it easier but this is work in progress.

What is wrong with the name of testing data storage?

Cheers,

Sven

@clviper
Copy link
Collaborator Author

clviper commented Dec 14, 2016

Hi @sushi2k. When reading the index (https://github.com/OWASP/owasp-mstg/blob/master/README.md) all the chapter .md files are located in the /document root folder except Testing Data Storage that is located in the /Document/Testcases/. Looking at the index, all the chapters .md file names are in the format of 0x-NAME.md. This chapter because is stored in a different folder has a completly differente name (0x00_OMTG-DATAST.md)

@clviper
Copy link
Collaborator Author

clviper commented Dec 14, 2016

Going to close this, already talked in Slack regarding this issue.

@clviper clviper closed this as completed Dec 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants