Testing package by a namcap

Hello
While testing a package by the namcap I get:
Traceback (most recent call last):
File "/usr/lib/python3.2/runpy.py", line 160, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python3.2/runpy.py", line 73, in _run_code
exec(code, run_globals)
File "/usr/lib/python3.2/site-packages/namcap.py", line 265, in <module>
process_realpackage(package, active_modules)
File "/usr/lib/python3.2/site-packages/namcap.py", line 118, in process_realpackage
rule.analyze(pkginfo, pkgtar)
File "/usr/lib/python3.2/site-packages/Namcap/rules/shebangdepends.py", line 112, in analyze
pkglist, orphans = findowners(scriptlist)
File "/usr/lib/python3.2/site-packages/Namcap/rules/shebangdepends.py", line 84, in findowners
if scriptpath in pkg.files:
UnicodeDecodeError: 'utf8' codec can't decode byte 0xfc in position 45: invalid start byte
Unfortunately I don't know Python and I don't know with what it's bound.
I use namcap-3.1 and python-3.2.2.
edit:
Temporarily I installed namcap from [testing] and it works. So it must be bug for 3.1 version.
Last edited by dracorp (2011-10-30 22:09:56)

well.. what pops out immediatly is that you didnt calculate first how long the loop itself takes.
meaning.. in the time result that you get, there are also all the loop operations.
measure an empty look running the same number of times and reduce it from your result.
by the way, do you know an easy way to decide if a string can be a valid class name?

Similar Messages

Test Package in Test Management tab of Change Document

Hi Expert,
When we test on CHARM, we realized that the test package in test management tab can only be
attach before the developer change the status to "Pass normal change to
test". Is this standard or can we do any configuration to allow the
test package be attach during "Test for Preliminary Input" status?
Thanks
Best Regards
Remy

Hi,
I manage to solve this issue as below,
Go to SPRO
>SAP Solution Manager Implementation Guide
>SAP Solution Manager
>Capabilities (Optional)
>Change Control Management
>Standard Configuration
>Change Request Management Framework
>Adjust UI objects by User Status
Thanks
Best Regards
Remy

Unit testing packages in sql developer

It appears that the specify parameters window is blank for packaged functions which means the test call fails when run. Is this a grant or synonym issue ( or something similar ) or is there an issue with testing packages via the unit test interface of sql developer. Thanks in advance.

Seems that you cannot right click on the packaged schema object from the schema connection i.e. you have to create the test from the unit test tab and then choose the object type i.e select packages and then the packaged function or procedure. This method results in the Specify Parameters window having the correct signature displayed. Procedures or methods can be created via the unit test tab or the active connection tab.

Can I Test the Test Package Created in SolMan Directly from ECC?

Hi,
the test plan and test packages are created in Solution Manager. The Test Packages are comprised of transactions (on ECC).
(The business scenarios and processes are defined in Solar01, ECC is defined as logical component and assigned to every tx, the test case description is uploaded in Solar02,...)
The needed Trusted RFC (to enable the tester to start the tx from within SolMan) is running late, but I can see that STWB_WORK tx is also available in ECC.
Of course - when I open it in ECC (logged on as a test user - defined in test package in SolMan) the test package is empty in ECC.
What kind of connection is there within STWB_WORK in ECC and SolMan?
Can one somehow "transfer" the packages from SM to ECC, so the tester can start to test the transactions from ECC directly?
Is it possible to see the results and status overview in SolMan during and after testing?
Thank you in advance,
cheers,
Nenad

Hi
You getting confused between old ECC test workbench and Solution Manager Test workbench.
Test workbench is present there from r/3 version onwards.
When you are performing testing via solman then you have to use the test packages assign to you in STWB_WORK which has the relevant transaction and doc for you to test
here you upload the test result and update status .Later any PM can generate report for overall testing including entire landscape and not one system.
But remember it has got no connection to ur r/3 workbench
The diff between 2 is...solman test workbench is for entire landscape including BI R/3 ECC any other system ...but in r/3 etc the workbench is alone and obsolete now is used for standalone testing.
Hope it carifies ur doubt completely
Regards
Prakhar

The test package does not point to the correct logical system

Hello,
I have defined SMSY logical componant, I have copied project1 to project2.
I have changed within the system landscape of project2, the logical componant.
I have also defined a project plan, and the test packages.
Hence, the test packages still do not point to the logical component that is defined in the landscape...
I must have missed something !
Can you help ?
Thanks a lot

hi
try following
1 check in smsy the logical component is correctly defined with clients dev qa and prd
2 same logical component is assigned to solar_project_admin
3 Project IMG is generated in the respective system
4 in solar01 check the logical component is shown correctly
5 Re- Generate the test plan once
hope above steps will resolve issue
regards
prakhar

Regenerating test packages in Solution Manager 4.0 after blueprint changes.

Hello,
This is the scenario.
A test plan and test package (1 process = 1 test package) have been created.
The blueprint has changed and a new step has been added to the process (the process that has already been assigned into a test package.
How do you get that new task/step into the test package??
Current situation:
I've managed to regenerate the test plan with the new task listed under the process. However when I go into change test package the new process is NOT there. Why is that? Can I had a new step to a package or not?
Regards
Dan

You must go down to the transaction leveland click and then regenerate it will then be eligible in the package for regeneration.

Transport of Test Plan / Test Packages

Dear all,
We intend to transport a test plan with all test packages from the development Solution Manager to the productive Solution Manager because in the productive Solution Manager no configuration is allowed.
We are using the Solution Manager functionality to execute manual testing in the following way:
On SOLAR02 the project 'FOUNDATION' is stored. The project 'FOUNDATION' has been migrated from a outstanding sandbox Solution Manager system to all three Solution Manager Systems: DEV, TEST and PROD. Test scripts have been uploaded on the 'test cases' tab of the respective business process branch.
In the development Solution Manager SMD a test plan has been generated using the uploaded test scripts mentioned above.
On the quality assurance Solution Manager the same project 'FOUNDATION' is stored and the same test scripts are uploaded on the same branches.
When the test plan is transported (using the recommended STWB_2 transport functionality) from the development SM to the quality assurance SM there are two issues.
1. The transported test plan cannot be edited / regenerated anymore. An error message "The specified structure does not exist" is displayed. Message number is SOLAR056.
2. The transported packages can be assigned to users but no notes can be added to the test cases. The error message is: "Unable to find template". Message number is SOFFICEINTEGRATION231.
It seems that the transported test plan cannot retrieve the underlying project structure, even it is identical to the project structure of the development SM.
This problem is urgent to us, as the test phase is starting next week.
Thank you very much for your support.
Best Regards,
Marc Reinhardt

Hello Marc,
We have experienced similar problems. A transport of the test plan and copies of the test plans have resulted in us loosing status values and test notes.
I was informed it had to do with the fact the information is stored in the GUI. How I don't know, I am not a technical person.
I was wondering if you may have encountered the similar problems I have had above and found ways around it.
You can reach me at [email protected] as well.

Test packages cant be created in locked system

I am using project management part of solution manager, & because the info structures are sap objects, I have to transport any change to a test package. I cannot create them in the production system as it is locked to changes. Other sap objects lets you tick the current settings box in sobj & then sap treats it like master data (which in reality this is !!)
Has any found a way around this, I think it is crazy to have to transport test packages

Rajesh,
Answer is very simple. I did get same kind of problem. It is very simple answer depending on your R3 version.
Use password all capital letters. Don't include any small letter at all. unlock your user id and change password to capital letter. BW doesn't like small and capital letter mix. this bug is fixed in ECC 6.0
<removed_by_moderator>
*Do not ask for points
Read the "Rules of Engagement"
Regards
RK
Edited by: Juan Reyes on May 21, 2009 9:30 AM

Error in Test Package

Hi,
I created a Test Plan and created some 10 Test Packages under it.
In a particular Test Package, I have 25 Test Cases. All the Test Cases are in UNTESTED State.
When i check the STATUS ANALYSIS for that Test Package, STATUS INDICATOR, STATUS TEXT & STATUS VALUE is not getting displayed for 10 TestCases in that . All these 3 fields are blank. For rest of the 15 Testcases, all these fields are shown up with values.
What could be reason for this?
Thx,
Waseem.

HI Prakhar,
Are the test cases modified in solar02 or newer version is uploaded for this test cases.
No. Test Cases are not modified.
When i regenerate that particular Test Package again, same error.
But, i tried copying the TEST PLAN and Generate Test Packages. It works fine. But i can't regenerate the whole TEST PLAN, since some of the Test Packages are in Testing phase; regenerating will remove all the status.
What can be the solution for this?
Thx,
Waseem.

Sequence in Test Package

Hi,
I have a sequence in a test package test1, test2, test3 say. The status and status value in the tester worklist is working i.e if you try execute test3 before test2 get message 'previous test case not yet finished'.
However, the 'ready to test' tick has decided to have it's own sequence of test1, test3, test2 so when test1 is marked as 'test ended' it moves to test3 looking like test3 is next to test when it's not!!
any ideas?
thanks

Hi,
Your worklist seems to be ok: the test cases are displayed in the order you need: test1, test2, test3 according to the sequence numbers 1, 2, 3.
But the 'ready to test' does not mark test2 as the next test case to be ready for test after the test1 has received the status 'test ended'.
One reason for this is: You have assigned the test cases test1 and test3 to the user TESTER1 and the test case test2 to the user TESTER2. Then TESTER2 sees in his worklist that test2 is marked to be ready for test. TESTER1 can see his next test case assigned to him to be ready for test. Is that describing your problem?
Therefore I have removed the confusing 'ready to test' information and have provided the 'test end' information instead for default settings of the layer for the worklist.
Best regards,
Adelbert

Test Package - Assignment to different tester

hi to everybody,
I'm using STWB_2 and STWB_WORK during test in an implementation project. I have created a test case with different process steps. Some of these steps are to be executed by a key user, other by another key user. How can I assign the different tester inside the test package. I would like to show this information when the testers display the package. Any idea????
Thanks a lot
lelio

Hi Lelio,
Ok. So, you have already considered the Package creation at Transaction Code Level.
One suggestion is, to let the first tester finish his/her transaction, have a test step called 'Create a message', let him/her create a message alerting the next tester to commence the next step. All such messages are with respect to a given 'Test' within a Test package - at Test document/ Transaction level, so they'll have the right 'context' when someone opens the message.
I know this isn't a great solution, but using a standard functionality for a different use.
Best regards,
Srini-
Hi Lelio,
I was going through [this|https://websmp107.sap-ag.de/~sapidb/011000358700000193922008E] presentation today - from SolMan Enterprise Edition and it seems like your query is answered by this version of SolMan. Please go to slides 8 to 11 of 25.
There is also a [SAP Tutor |https://websmp107.sap-ag.de/~sapidb/011000358700000183912008E.sim]file which explains how the new functionality works. It's great to see this - and I wish this was part of normal SolMan pack itself !
Of course, this would come at some extra cost. Perhaps, a case for you to consider at a later stage, or if your project/support organisation can spare that rightaway
Warm regards,
Srini
Edited by: Srinivasan Radhakrishnan on May 26, 2008 3:08 PM

Date assignement is absent in test packages.

Hi All,
I have created one project and related to that defined scenarios for the same.
Later when i created the test plan i got the scenarios with test cases.....and also with actual and plan dates which are coming from solar02 transaction.
When we generate the test plan and later create test packages dates are not appearing.
Please help and points will be rewarded.

Hello Prakhar,
the SAP Solution Manager - Test Workbench integration works as follows:
The assignments that you make on the Administration tab in transaction SOLAR02 are also visible in the Test Workbench STWB_2 transaction on the very same Administration tab. This holds true when generating test plans; when selecting the contents for a test package there is now way to seperately see planned/actual dates for there is no Administration tab available on this leve.
So if you have experienced this behaviour, the functionality works as it has been implemented.
The dates that you maintain in SOLAR01 and SOLAR02 indicate the planned and actual processing time for your scenarios, processes and processes steps. So this information may contain all the efforts for building up the appropriate process structure, assigning documentation, doing the configuration and creating and assigning test cases and so forth - depending on your project scope.
In the Test Workbench (STWB_2) your see all this Administration information as display only, including for example respective key word assignments. You can now go ahead and size and generate your test plan based on those structure filter criteria (status, project team members, keywords).
So to sum up: The Administration information gets displayed on the test plan level and can be used to appropriately generate your test plans. It is not, however, seperately displayed for test packages (test package level), which resemble a view on your test packages.
I hope this clarifies what you were looking for.
Best regards,
Doreen Baseler

SCAT - Tester in the Test Package

Hi! All Experts,
I have created a Test Package and assigned Tester to each Test Case. e.g.Data Entry Clerk to Test Script A, Approver to Test Script B.
However, when I run the Test Case in the Test Package, the system always logon as user "ALE-BATCH" and run the Test Scripts A and B.
Is it possible to logon as the Tester and run the Test Script ? E.g. logon as Data Entry Clerk and run Test Script A, then logon as Approver and run Test Script B ?
Thanks in advance for all the advise.

It is because I have picked a RFC Destination with default user id ALE-BATCH and password.
To solve this, I have to build another RFC Destination which will prompt for logon ID and password.

Error during execution in background: No Test Package Selected

We have created a test package and tried to run both in foreground (Goto -> Automatic Test -> Execute) and background (Goto -> Automatic Test -> Execute in background). We are pretty confident that the test case included in the package works well.
Foreground run is successful. However, when we try to run using background mode, we get the error "No Test Package Selected." What could be the possible issue for this?

Unsigned applets are not allowed to access the file system...
http://java.sun.com/developer/technicalArticles/Security/Signed/

Can't create Test package

Hello, After updating up to 22 version new problem has apeared in Test management. I can't create test package in newly created Test Plan. There are disabled buttons like a "create package" and "change package" on the "Test package management" screan. I try to make it with SAP_ALL authorisations.

Try using this authorization SAP_SOL_PROJ_ADMIN_ALL
some authorizsations are not included in the SAP_ALL
hope it helps.

Testing package by a namcap

Similar Messages

Maybe you are looking for