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

Integrate data flow information (PROC SCAPROC) into test report #13

Open
SamuelMelm opened this issue Jul 18, 2023 · 1 comment
Open

Integrate data flow information (PROC SCAPROC) into test report #13

SamuelMelm opened this issue Jul 18, 2023 · 1 comment
Labels
enhancement New feature or request postponed Issue is not in the currennt scope

Comments

@SamuelMelm
Copy link
Contributor

The execution of a test candidate as part of the test scenario could additionally be documented as a data flow diagram (or simpler, just listing), generated from the output of PROC SCAPROC and attached to the test scenario report. This would further enhance program documentation.

Originally created on SourceForge by amangold - 23.07.2012, 12:49
@KLandwich
Copy link
Contributor

KLandwich commented Dec 5, 2023 •
edited
Loading

The result of PROC SCAPROC is not meant to be evaluated by humans.
There is a lot of technical output from PROC SCAPROC that is not easily distinguished from program output.
Results from test run for SASUnit examples are stored here:
Projekt folder for SASUnit: SASUnit_Example_PROC_SCAPROC_Results.zip
This issue need refinement before it can be implemented.

@KLandwich KLandwich added enhancement New feature or request deprecated Issue is no longer relevant postponed Issue is not in the currennt scope and removed deprecated Issue is no longer relevant labels Feb 14, 2024
SamuelMelm pushed a commit that referenced this issue Feb 26, 2024
@KLandwich
Merge pull request #13 from HMS-Analytical-Software/feature/18-bug-sa…
9f5ae8f 
…sunitcfg-not-used-in-sas-subprocess

Feature/18 bug sasunit cfg not used in sas subprocess
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request postponed Issue is not in the currennt scope
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SamuelMelm @KLandwich