You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Is they any way we can get the UTPLSQL historical runs by using RUN ID and their coverage #192
Is they any way we can get the UTPLSQL historical runs by using RUN ID which gets generated automatically and their coverage using the inbuilt tables of UTPLSQL.
used the below query but could not find any data in the result of below query
select owner, name, type
from dbmspcc_runs r
join dbmspcc_units u
on r.run_id = u.run_id
Hey @venkat-kasula - thanks for your patience. The last months have been a bit rough.
There is no way to get data about historical runs in utPLSQL or the cli. This is a design decision, because storing the outcomes of a run is the task of the surrounding CI environment (e.g. Jenkins).
There is a lightweight Apex solution you might be interested in: http://github.com/triologygmbh/utPLSQL-APEX
There is also an even more lightweight way of storing your run results in the database, though you cannot do that via the cli right now (well, you could create your own reporter to do that, but that's a bit more effort):
createtableut_runs (
run_timestamp timestamp,
output varchar2(4000)
);
insert into ut_runs
selectcurrent_timestamp, column_value from table(ut.run());
Activity
venkat-kasula commentedon Feb 23, 2021
@pesse can you please help me here
pesse commentedon Jun 10, 2021
Hey @venkat-kasula - thanks for your patience. The last months have been a bit rough.
There is no way to get data about historical runs in utPLSQL or the cli. This is a design decision, because storing the outcomes of a run is the task of the surrounding CI environment (e.g. Jenkins).
There is a lightweight Apex solution you might be interested in: http://github.com/triologygmbh/utPLSQL-APEX
There is also an even more lightweight way of storing your run results in the database, though you cannot do that via the cli right now (well, you could create your own reporter to do that, but that's a bit more effort):