UNISYS DAILY DIARY,MAINTAINNING NOTES IMP FHPL PORTAL

 ODS_CW--final DB


ST and MT data into ODS_CW


already Mt data --datasourceid=??--ODS_CW

we are adding new ST data---datasourceid=??--ODS_CW


data from source to stage and sync(ST)---->ods_cw

data from source to stage and sync(MT)--->ODS_CW




ODS_LOG.DBO.SOURCETABLES



                                                                   519804(login of health care)

                                                                   fhmo24ma(111996)*



normal testing Process,data testing pipeline

automated data pipeline ,changes automatic when the deployment is changes 


scope: validate the data


Azure devops create user story,work data,meta data in  manually testing 

sprint test plan 

master test plan


data comes_____________________

source>>>>>>Raw >>>>>>bronze(mapping)>>>>>Silver(aggregare operation)>>>>Models(Analysis server,)>>>>>>>>>>

   Powerbi(rate the data to models)>>>>>>>>downstream




Raw---ODS_cw

                          ODS_STG_SILVER



models---















------------------TEAMS---------------------------------


BAU----UNISYS(MT-ST)SSMS 





FDL----(AZURE)DATA LAKE,NOTE PAD 







Schema Defination---->>>>

MT(multi tanent)----->>>>

St(single tanent)---->>>>




SIT TEST PLANNING







PMO PROJECT---





---------------------------------------------------------------UCARE pROJECT NAME MASTER TEST PLAN TEMPLATE-------------------------------------------------------



1.Master Test Plan describes the appropriate strategies, process, methodologies used to plan, organize, execute and manage testing of the UCARE Data Platform implementation to include the data warehouse and BI reports.


2.The general objective for testing is to validate and verify each process of the BI project and ensure that they are supported by existing business processes and rules. 


3.The general scope of QA work for the [Project Name] includes planning, execution, implementation


4.



        1. Independently validate information upstream, downstream, and within ETL 

        2. Detect source errors and prevent them from propagating to targets  

        3. Assure data accuracy and data quality with a focus on target data

4. Ensure that all data represented by data maps and process flows are deployed successfully 

5. Ensure successful loads of source data into each destination repository 

6. Ensure that all data validations have been performed 

7. Ensure that all the Lookup checks have been accomplished 

8. Pre-screening tests: Verify for missing values, duplicates, data formats etc. 

9. Completeness tests: Enable count comparisons between all sources and associated targets 

10. Uniqueness tests: Verify for the uniqueness constraint defined data requirements 

11. Referential integrity tests: Verify that complete records have been copied and that technical as well as logical integrity is maintained 

12. Reconciliation tests: perform complete source-to-target comparisons including file-to-database and database-to file comparisons 

13. Define the test approach/strategy as described in the project Master Test Plan (MTP)

14. Develop detailed test plans that describe the appropriate test coverage, and ensure each release is sufficiently tested prior to production 

15. Develop automation strategy and identify tools (ex., ETL Validator) for testing that requires minimal maintenance  

16. Identify the test environments that will be needed to sufficiently test the DW and BI application.  

17. Prepare/identify and execute test cases in accordance with the approved Test Plans. Document actual test results as part of the test execution activities.  

18. Provide developers with quick feedback. This can be accomplished by including automation in the CI process. 

19. Identify the process(es) that will be used to document, track, report and manage issues that are identified during the testing activities 

20. Achieve an acceptable level of risk that balances cost of testing against the cost and likelihood of potential failures.  













Comments

Post a Comment

Popular posts from this blog

java chapter11 practice question on abstruct class and interfaces

  /* Chapter 11 - Practise Set 1... Create an abstract class Pen with methods Write () and refill 1) as abstract methods 2... Use the Pen Class from Q1 to create a Concrete class fountain Pen with additional method change Nibl) 3...Create a class Monkey with jump () and bitel) methods. Create a class Human which inherits this Monkey class and implements Basic Animalinterface with eati) and sleep methods. 4.... Greate a class Telephone with ring() liftus and disconnect ( methods as abstract methods Create another class Smart Telephone and demonstratepolymorphism 5.....Demonstrate polymorphism Msing monkey class from Quess 3. 6.......Create an Interface TV Remote and use it to inheritanother Interface Smart Tv Remote 7...... Create a Class Tv which implements Tv Remote interface qsn 6 */ package com.company ; //programe 1 abstract class Pen { abstract void Write (); abstract void Refill (); } //programe 2 class FountainPen extends Pen { void Writ
Read more

java practice set 8

  questions: /* 1. Create a class Employee with the following properties and methods: Salary (property) (int) getSalary (method returning int) name (property) (String) getName (method returning String) setName (method changing name) 2. Create a class cellphone with methods to print “ringing…”, “vibrating…”, etc. 3. Create a class Square with a method to initialize its side, calculating area, perimeter etc. 4. Create a class Rectangle & problem 3. 5. Create a class TommyVecetti for Rockstar Games capable of hitting (print hitting…), running, firing, etc. 6. Repeat problem 4 for a circle. */ answers package com.company; class Employee{ int salary; String name; public int getSalary(){ return salary; } public String getName(){ return name; } public void setName(String n){ name = n; } } class CellPhone{ public void ring(){ System.out.print
Read more

new stored procidure with interval and frequery code

 CREATE procedure  [dbo].[SP_Baxter_CSAT]                                                                                                             AS                                                            BEGIN            DECLARE @ExtractIdOut INT                                                                   DECLARE @EndDt DATETIME2                                 DECLARE @runDate DATETIME2                                 DECLARE @RecordCount INT = 0                                                                 DECLARE @ProcedureName SYSNAME = OBJECT_NAME(@@PROCID)                                              DECLARE @intErrorCode INT                                                                 Declare @returnCode int = 0                                                                 DECLARE @ExtractProcessControlId UniqueIdentifier                                                                 SET NOCOUNT ON;                              BEGIN TRY           --Log the
Read more