[svn:osmf:] 10648: Adding first MAST unit tests and added some ASDocs

Revision: 10648
Author:   [email protected]
Date:     2009-09-28 10:28:12 -0700 (Mon, 28 Sep 2009)
Log Message:
Adding first MAST unit tests and added some ASDocs
Modified Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/.actionScriptProperties
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/MediaFrameworkTests.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/adapter/MASTAdapter.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/loader/MASTDocumentProcessedEvent. as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/loader/MASTDocumentProcessor.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/loader/MASTLoadedContext.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/loader/MASTLoader.as
    osmf/trunk/plugins/MASTPlugin/org/openvideoplayer/mast/managers/MASTConditionManager.as
Added Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/mast/
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/mast/MASTTestConstants.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/mast/loader/
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/mast/loader/TestMASTLoade r.as
    osmf/trunk/plugins/MASTLib/
    osmf/trunk/plugins/MASTLib/.actionScriptProperties
    osmf/trunk/plugins/MASTLib/.flexLibProperties
    osmf/trunk/plugins/MASTLib/.project
    osmf/trunk/plugins/MASTLib/src/

These are automated emails from the OSMF forums. To unsubscribe, go here:
http://forums.adobe.com/community/opensource/osmf/commits
-- Brian

Similar Messages

[svn:osmf:] 11233: Add downloadable related unit tests for MediaPlayer

Revision: 11233
Author:   [email protected]
Date:     2009-10-28 11:29:23 -0700 (Wed, 28 Oct 2009)
Log Message:
Add downloadable related unit tests for MediaPlayer
Modified Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/TestMediaPlayer.as
Added Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/utils/MockMediaElementWithDownloadab leTrait.as

Revision: 11233
Author:   [email protected]
Date:     2009-10-28 11:29:23 -0700 (Wed, 28 Oct 2009)
Log Message:
Add downloadable related unit tests for MediaPlayer
Modified Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/TestMediaPlayer.as
Added Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/utils/MockMediaElementWithDownloadab leTrait.as

[svn:osmf:] 15899: Attempted fix for unit tests failure.

Revision: 15899
Revision: 15899
Author:   [email protected]
Date:     2010-05-04 17:21:06 -0700 (Tue, 04 May 2010)
Log Message:
Attempted fix for unit tests failure.
Modified Paths:
    osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as

[svn:osmf:] 10517: Last set of unit tests for ListenerProxyElement.

Revision: 10517
Author:   [email protected]
Date:     2009-09-22 15:47:18 -0700 (Tue, 22 Sep 2009)
Log Message:
Last set of unit tests for ListenerProxyElement.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/proxies/ListenerProxyElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/proxies/TestListenerProxy ElementAsSubclass.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/utils/DynamicListenerProx yElement.as

Revision: 10517
Author:   [email protected]
Date:     2009-09-22 15:47:18 -0700 (Tue, 22 Sep 2009)
Log Message:
Last set of unit tests for ListenerProxyElement.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/proxies/ListenerProxyElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/proxies/TestListenerProxy ElementAsSubclass.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/openvideoplayer/utils/DynamicListenerProx yElement.as

[svn:osmf:] 14994: Fix 10.1 unit test compile errors.

Revision: 14994
Revision: 14994
Author:   [email protected]
Date:     2010-03-24 11:35:55 -0700 (Wed, 24 Mar 2010)
Log Message:
Fix 10.1 unit test compile errors. Remove unused constants.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataNamespaces.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/f4mClasses/TestManifestParser.as
    osmf/trunk/framework/OSMFTest/org/osmf/net/TestNetStreamUtils.as

Revision: 14994
Revision: 14994
Author:   [email protected]
Date:     2010-03-24 11:35:55 -0700 (Wed, 24 Mar 2010)
Log Message:
Fix 10.1 unit test compile errors. Remove unused constants.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataNamespaces.as
    osmf/trunk/framework/OSMFTest/org/osmf/elements/f4mClasses/TestManifestParser.as
    osmf/trunk/framework/OSMFTest/org/osmf/net/TestNetStreamUtils.as

[svn:osmf:] 11014: Temporarily disable failing unit test.

Revision: 11014
Author:   [email protected]
Date:     2009-10-19 16:09:18 -0700 (Mon, 19 Oct 2009)
Log Message:
Temporarily disable failing unit test.
Modified Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/MediaFrameworkTests.as

[svn:osmf:] 13916: Added DynamicDRMTrait, Composite Unit tests for parallel and serial compositions.

Revision: 13916
Revision: 13916
Author:   [email protected]
Date:     2010-02-01 16:42:09 -0800 (Mon, 01 Feb 2010)
Log Message:
Added DynamicDRMTrait, Composite Unit tests for parallel and serial compositions. Bug fixes in CompositeDRMTrait.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/composition/CompositeDRMTrait.as
    osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as
    osmf/trunk/framework/OSMFTest/org/osmf/utils/DynamicMediaElement.as
Added Paths:
    osmf/trunk/framework/OSMFTest/org/osmf/composition/TestParallelElementDRMTrait.as
    osmf/trunk/framework/OSMFTest/org/osmf/composition/TestSerialElementDRMTrait.as
    osmf/trunk/framework/OSMFTest/org/osmf/utils/DynamicDRMTrait.as

[svn:osmf:] 12257: Extending trait resolver related unit tests, and fixing found malfunctions.

Revision: 12257
Revision: 12257
Author:   [email protected]
Date:     2009-11-27 13:01:04 -0800 (Fri, 27 Nov 2009)
Log Message:
Extending trait resolver related unit tests, and fixing found malfunctions.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/media/DefaultTraitResolver.as
    osmf/trunk/framework/MediaFramework/org/osmf/media/MediaElement.as
    osmf/trunk/framework/MediaFramework/org/osmf/media/MediaTraitResolver.as
    osmf/trunk/framework/MediaFramework/org/osmf/utils/MediaFrameworkStrings.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/MediaFrameworkTests.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/audio/TestAudioElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestSerialElement.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/video/TestVideoElement.as
Added Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/MediaTraitResolverBaseTestCase .as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/TestDefaultTraitResolver.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/media/TestMediaTraitResolver.as

[svn:osmf:] 12425: Extending unit tests, and fixing a bug.

Revision: 12425
Revision: 12425
Author:   [email protected]
Date:     2009-12-03 04:22:59 -0800 (Thu, 03 Dec 2009)
Log Message:
Extending unit tests, and fixing a bug.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/metadata/CompositeMetadata.as
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/metadata/TestCompositeMetadata.as

Difference between unit testing and integration testing

What is the difference between unit testing and integration testing in SAP? Is unit testing takes place in Dev client and integration testing takes place in QA system?
Please clarify
thanks

Hello Krishen,
unit testing means veryfiingsmall / the smallet pieces of software, while integration testing checks the overall functionality of applications. Within the AS ABAP the tool ECATT + manual tests is used for integration tests and the ABAP Unit language integration for unit testing.
When, Who, Where tests are carried out is ultimately a personal decision. As unit tests are operate even under heavy development they are often the first choice for developers, but the unit tests can also serve for regression tests over a long period. Integration tests tend too be created and executed in later stages as they require often a certain majurity of the software under test.
Beside the mentioned links you may check out ABAP Unit infos also in the Wiki.
https://wiki.sdn.sap.com/wiki/display/HOME/ABAP+Unit
Best Regards
Klaus

Unit tests and QA process

Hello,
(disclaimer : if you agree that this topic does not really belong to this forum please vote for a new Development Process forum there:
http://forum.java.sun.com/thread.jspa?forumID=53&threadID=504658 ;-)
My current organization has a dedicated QA team.
They ensure end-user functional testing but also run and monitor "technical" tests as well.
In particular they would want to run developer-written junit tests as sanity tests before the functional tests.
I'm wondering whether this is such a good idea, and how to handle failed unit tests:
1) Well , indeed, I think this is a good idea: even if developer all abide by the practice of ensuring 100% of their test pass before promoting their code (which is unfortunately not the case), integration of independant development may cause regression or interactions that make some test fail.
Any reason against QA running junit tests at this stage?
However the next question is, what do they do with failed tests : QA has no clue how important a given unit test is with regard to the whole application.
Maybe a single unit test failed out of 3500 means a complete outage of a 24x7 application. Or maybe 20% of failed tests only means a few misaligned icons...
2) The developer of the failed package may know, but how can he communicate this to QA?
Javadocing their unit testing code ("This test is mandatory before entering user acceptance") seems a bit fragile.
Are there recommended methods?
3) Even the developer of the failed package may not realize the importance of the failure. So what should be the process when unit tests fail in QA?
Block the process until 100% tests pass? Or, start acceptance anyway but notify the developper through the bug tracking system?
4) Does your acceptance process require 100% pass before user acceptance starts?
Indeed I have ruled out requiring 100% pass, but is this a widespread practice?
I rule it out because maybe the failed test indeed points out a bad test, or a temporary unavailability of a dependent or simulated resource.
This has to be analyzed of course, as tests have to be maintained as well, but this can be a parallel process to the user acceptance (accepting that the software may have to be patched at some point during the acceptance).
Thank you for your inputs.
J.

>
Any reason against QA running junit tests at this
stage?
Actually running them seems pointless to me.
QA could be interested in the following
- That unit tests do actually exist
- That the unit tests are actually being run
- That the unit tests pass.
This can all be achieved as part of the build process however. It can either be done for every cm build (like automated nightly) or for just for release builds.
This would require that the following information was logged
- An id unique to each test
- Pass fail
- A collection system.
Obviously doing this is going to require more work and probably code than if QA was not tracking it.
However the next question is, what do they do with
failed tests : QA has no clue how important a given
unit test is with regard to the whole application.
Maybe a single unit test failed out of 3500 means a
complete outage of a 24x7 application. Or maybe 20%
of failed tests only means a few misaligned icons...
To me that question is like asking what happens if one class fails to build for a release build.
To my mind any unit test failure is logged as a severe exception (the entire system is unusable.)
2) The developer of the failed package may know, but
how can he communicate this to QA?
Javadocing their unit testing code ("This test is
mandatory before entering user acceptance") seems a
bit fragile.
Are there recommended methods?Automatic collection obviously. This has to be planned for.
One way is to just log success and failure for each test which is gathered in one or more files. Then a seperate process munges the result file to collect the data.
I know that there is a java build engine (add on to ant or a wrapper to ant) which will do periodic builds and email reports to developers. I think it even allows for categorization so the correct developer gets the correct error.
>
3) Even the developer of the failed package may not
realize the importance of the failure. So what
should be the process when unit tests fail in
QA?
Block the process until 100% tests pass? Or, start
acceptance anyway but notify the developper through
the bug tracking system?
I would block it.
4) Does your acceptance process require 100% pass
before user acceptance starts?
No. But I am not sure what that has to do with what you were discussing above. I consider unit tests and acceptance testing to be two seperate things.
Indeed I have ruled out requiring 100% pass, but is
this a widespread practice?
I rule it out because maybe the failed test indeed
points out a bad test, or a temporary unavailability
of a dependent or simulated resource.Then something is wrong with your process.
When you create a release build you should include those things that should be in the release. If they are not done, missing, have build errors, then they shouldn't be in the release.
If some dependent piece is missing for the release build then the build process has failed. And so it should not be released to QA.
I have used version control/debug systems which made this relatively easy by allowing control over which bug/enhancements are included in a release. And of course requiring that anything checked in must be done so under a bug/enhancement. They will even control dependencies as well (the files for bug 7 might require that bug 8 is added as well.)

Unit testing and system integration testing for crystal report

Hi gurus,
I am creating crystal report by oracle procedure, will you please tell me how to do unit testing and system integration testing? appreciate very much.

The focus of this forum is report design. The actual testing of reports would be subject to your own internal policies and procedures.
Jason

Unit Testing and Integrating testing In HR

Dear Sap Gurus,
Would you be kind enough to give me an example of unit testing and integrating testing?? what do you test, eg..TC and what else.. what happened.??. And also an example of Integrating testing ..and an example ....I know what unit and integrating test is ..and with a good example, i will have a great idea about it ...thanks a lot.

Hi Pooja
Unit Testing:
A process for verifying that software, a system, or a system component performs its intended functions.
Unit transactions are tested against their own specifications and design documents.
Integration Testing
An orderly progression of testing in which software elements, hardware elements or both are combined and tested until the entire system has been integrated.
Integration tests deal mainly with the testing of cross-application process chains in addition to transactions and business processes. The process models and the test cases derived from these form the basis of these tests.
Regards
Vijay

When building an application unit tests are added to a support directory

Why are unit tests (.lvtest files) added to a support directory when building an application? I cannot find a way to exclude them from the support directory.

I'd imagine this is happening to you because they are in the "Dependencies" section of your project file (*.lvproj). Is this correct?
If so, you should add them to your project file somewhere. Then you will be able to prevent them from being installed. In my experience LabVIEW grabs files it thinks are nesecary from the Dependencies list and installs them in a support directory.

Unit Testing and APEX Global Variables

We've recently started to unit test our database level PL/SQL business logic.
As such we have a need to be able to simulate or provide output from PL/SQL APEX components in order to facilitate testing of these components.
Some of the most obvious portions that need simulation are:
1. The existence of a session
2. The current application ID
3. The current page ID.
We currently handle requirement #1 by using apex_040100.wwv_flow_session.create_new
We handle 2 and 3 using the apex_application.g_flow_id and g_flow_step_id global variables.
I'm just wondering, how safe is it for us to use wwv_flow_session.create_new to simulate the creation of a session at testing time for those things which need a session?
I've also noticed that there are apex_application.get_application_id and apex_application.get_page_id functions whose output is not tied to the global variables (at least in our current version).
Is it safe for us to expect that we can set these global variables for use in testing or is apex moving to get_application_id and get_page_id functions away from global variables?
Will there be corresponding set_application_id and set_page_id functions in the future?
Sorry for the question bomb. Thanks for any help.

My first question would be why do you need to establish a session to test your PL/SQL?
wwv_flow_session is a package internal to APEX, and you should probably leave it be.
The get_application_id procedure you refer to is in apex_application_install, which is used for scripting installation of applications - not get/set of page ID like you're describing.
If you're uncomfortable using apex_application.g_flow_id, you can use v('APP_ID') or preferably pass the app_id/page_id as parameters to your procedures.
Your question seems to have a few unknowns, so that's the best I can describe.
Scott

[svn:osmf:] 10648: Adding first MAST unit tests and added some ASDocs

Similar Messages

Maybe you are looking for