APL Wiki|
Size: 2221
Comment: Standards for test cases added
|
Size: 1709
Comment: Not vendor specific anymore, but needs classes
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Note that this is a pure Dyalog project. Note also that by definition only scripts (either class- or namespace-scripts) can be part of APLAPL. Scripts in this category '''must''' contain a Copyright notice according to the [[http://en.wikipedia.org/wiki/Mit_license|MIT license]] conditions. |
|
| Line 10: | Line 6: |
| To become part of the APLAPL project, one must ensure that proper test cases are written and executed before the class is published. Although that does not guarantee that the scripts are free of bugs, this certainly decreases the danger of bugs. | Sub-projects of APLAPL '''must''' follow certain [[AplAplStandards | standards]] |
| Line 12: | Line 8: |
| == Test cases: follow the standards! == | The columns "Win" and "Linux" are checked if the software is designed for running under this operating system '''and''' comes with test cases for that environment. |
| Line 14: | Line 10: |
| <<SeeSaw(section="testcasestd", toshow="<<Show>> the details", tohide="<<Hide>> the details", bg="#FEE1A5", speed="Slow")>> | By defenition all APLAPL projects must be classes, ot at least scripts. For the time being (2009-01) this restricts the APLAPL projects to Dyalog and APLX. |
| Line 16: | Line 12: |
| {{{{#!wiki seesaw/testcasestd/testcasestd-bg/hide | <<BR>><<BR>> |
| Line 18: | Line 14: |
| * All test cases are supposed to be in a namespace {{{#.TestCases}}}. * At least there is one sub-namespace: "Test_001". Depending on the complexity of the tests, there may be up to 999 different test cases. * Every sub-namespace "Test_00n" is supposed to have a function "Run" which executes the test case. * There should be a function {{{#.TestCases.RunAll}}} which is supposed to run all test cases in one go. * When a test fails, let it stop. }}}} ##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||''''''|| ||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Needs .NET'''|| ||[[APLTeamUtils]]||General utilities||Dyalog||APL Team||'''No'''|| ||[[ADOC]]||Automated Documentation Generation||Dyalog||APL Team||'''No'''|| ||[[Hash]]||Managing key/value-pairs||Dyalog ||APL Team||'''No'''|| ||IniFiles||Dealing with INI files||Dyalog||APL Team||'''No'''|| ||[[Logger]]||Writing Log Files||Dyalog||APL Team||'''No'''|| ||[[WindowsEventLog]]||Dealing with the Windows Event Log||Dyalog||APL Team||'''Yes'''|| ||[[WinFile]]||Dealing with files and directories||Dyalog||APL Team||'''No'''|| ||[[WinReg]]||Dealing with the Windows Registry||Dyalog||APL Team||'''No'''|| |
||<rowclass="odd" tablestyle="background:#ffe;font-size:small"> '''Name''' || '''Description''' || '''Originator''' || '''Dialect''' || '''Win''' || '''Linux''' || '''.NET<<BR>>required''' || ||[[APLTeamUtils]]||General utilities||APL Team||Dyalog|| (./) || {X} || {X} || ||<rowclass="odd">[[ADOC]]||Automated Documentation Generation||APL Team||Dyalog|| (./) || {X} || {X} || ||[[Hash]]||Managing key/value-pairs||APL Team||Dyalog|| (./) || {X} || {X} || ||<rowclass="odd">IniFiles||Dealing with INI files||APL Team||Dyalog|| (./) || {X} || {X} || || [[Logger]] ||Writing Log Files||APL Team||Dyalog|| (./) || {X} || {X} || ||<rowclass="odd">ShowChmHelp||Display help files and topics within help files||APL Team||Dyalog|| (./) || {X} || {X} || ||[[WindowsEventLog]]||Dealing with the Windows Event Log||APL Team||Dyalog|| (./) || {X} || (./) || ||<rowclass="odd">[[WinFile]]||Dealing with files and directories||APL Team||Dyalog|| (./) || {X} || {X} || ||[[WinReg]]||Dealing with the Windows Registry||APL Team||Dyalog|| (./) || {X} || {X} || |
APL Application Programming Library (APLAPL)
The basic idea behind APLAPL is to provide classes for every-day-problems programmers typically come across.
Sub-projects of APLAPL must follow certain standards
The columns "Win" and "Linux" are checked if the software is designed for running under this operating system and comes with test cases for that environment.
By defenition all APLAPL projects must be classes, ot at least scripts. For the time being (2009-01) this restricts the APLAPL projects to Dyalog and APLX.
Name |
Description |
Originator |
Dialect |
Win |
Linux |
.NET |
General utilities |
APL Team |
Dyalog |
|
|
|
|
Automated Documentation Generation |
APL Team |
Dyalog |
|
|
|
|
Managing key/value-pairs |
APL Team |
Dyalog |
|
|
|
|
Dealing with INI files |
APL Team |
Dyalog |
|
|
|
|
Writing Log Files |
APL Team |
Dyalog |
|
|
|
|
Display help files and topics within help files |
APL Team |
Dyalog |
|
|
|
|
Dealing with the Windows Event Log |
APL Team |
Dyalog |
|
|
|
|
Dealing with files and directories |
APL Team |
Dyalog |
|
|
|
|
Dealing with the Windows Registry |
APL Team |
Dyalog |
|
|
|
