When you are talking about the Test Status, there are two distinct status assigned to a Test.
- TS_STATUS: The test's current status. The values are from the Plan Status custom list. Typical values are: Ready, Besign, Imported, Repair.
- TC_EXEC_STATUS: The execution status of the test. The values are from the Status custom lsit. Typical values are: Not Completed, No Run, Passed, N/A, Failed
The first one can be seen within the Client easily in the details of a Test. The execution status was behind the scenes until the advent of Test Configurations. It can be seen in the Test Configurations tab of the Test Plan if you have a recent enough version of HP ALM. So that brings the question, which status are you talking about?
If you are talking about the Test status then there is no relation to the Test Lab as this just represents the readiness of the Test itself.
I'll assume therefore that you are talking about the execution status. You say that
The Execution status of scripts is different in Test lab and test plan
One scenario that this could happen is if you run the Test multiple times. Let's say you run it twice and it has a status of Failed first, then run it a second time and it Passed. You could be looking at the first execution which has a status of Failed, but the Test itself will show Passed. This is because the Test inherits the last execution status.
You also said
the scripts are passed in test lab but in test plan ,the execution
status shows no run or not completed
If it is No Run, then I don't have all of the information I need. The only case where it would be No Run is if it was never run (or possibly if it was run and then the Execution Status in the Test Lab was changed back to No Run). However, if you are seeing Not Completed this could be because you have multiple Test Configurations and you have run some and not others. When looking at requirements tied to a Test that has multiple configurations, you will see a rolled up status of Not Completed in this case. This may also be elsewhere in the system and specifically in the
TC_EXEC_STATUS. Each Test Configuration actually gets its own status in its own database table [
TEST_CONFIGS.TSC_EXEC_STATUS]. This is what you are seeing in the Client.
Without more information on what field you are talking about and under what conditions this is happening I cannot give a more definite or detailed answer. I hope this helps you solve your issue.