Day 01 - Scope, Existing App walk through, Task break down

Project : AnyAUT Code Level Framework Changes.


Minutes of Meeting 

9th July

  • Ramu leading the project. POC. 
  • Ground rules :
  • Participation
  • Active in project
  • Team work
  • Coding
  • Presentations 
  • And deadlines.
  • Inactive but good spectator
  • Keep positivity. Ex: Doubt vs Question?
  • Daily standup at 9a PT. 
  • Project Team meetings - you decide with your teams.
  • Team presentations.
  • Get a great chance to see where you lack and improve significantly. 


List of Features : 

  • Changing the Regression and the Run Result Excel to include a severity column
  • Classifying defects as Critical/Severe/Technical based on the failed test steps
  • Customizing the Extent Report to display the number of failed test cases based on severity
  • Triggering Email Alerts based on the severity of the defect
  • Implementing the CI/CD process for E2E automation of the regression suite with Github  and Jenkins
  • Optimizing the Remote M/C to kill chrome driver and chrome browser tasks to enhance system performance
  • Parallel Runs of regression suite for coverage of different user roles
  • Cross Browser Testing of the regression test cases. 
  • Refining the code to include additional features like screenshot for every step.
  • NEW Keywords for API Testing. RestAssured. JSON. CRUD. 
  • UI Launcher
  • Browser Options
  • Screenshot
  • Severity
  • Launch Configurations - Browser, Severity, Screenshot, Error Crawler. 


Features :

  1. Severity : Severity Level 1-6
  • Active developers who will get access to code. 
  • Other participants to test the progress.
  • Scope/Flow : 
  • Add severity column to the TC sheet (Col G[6]) - 
  • Code Change : 
  • Add severity Check Box to UICode.java [priority 2]
  • In PrepareTest, add severity column to the TS sheet (Col G[6]) matching the TC sheet. Update needs to be made in the TestRun_Name.xls in 
  • Sheet “TestCases” >>> Col G
  • Sheet “TestSteps”  >>> Col P. OPTIONAL. NOT NEEDED. As it will get updated for each TestStep in the runResult.xls 


  • After ExecuteTest, add severity column to the RunResults.xls (Col P) matching the TC sheet from TestRun_Name.xls
  • Add a pivot/macro to show TC Results Summary, by Severity or Criticality. NEW sheet in RunResult.xls
  • Need to decide on the Dashboard and Rules for the To-Fill-Cells-By-Code.
  • Skills required : 
  • UICode changes - Core Java, Java Swing
  • Severity - TestNG, Apache POI HSSF, Arrays and Lists/Dynamic Arrays, Excel
  • Collaborate - GitHub, Testing. BREAK by writing simple Regression Excels.
  • Selenium, RPA, Core Java, Java Swing, Frameworks, POM, TestNG, Coding, Apex, Testing, Manual Testing, Git/GitHub, API, Postman, JIRA, Cucumber, CI/CD, Jenkins, Rally, DevOps, MS Office, Excel

Divide into groups. 

  • Scope of work or 1 code/module together
  • Geo based???

2 Groups :

  • Developers : Core Java, Java Swing, TestNG, Apache POI HSSF, Arrays and Lists/Dynamic Arrays, Excel
  • QA Manual : User Stories, Scenarios. Break things, Creative over it. Less txt, more finding bugs. 


Fill this gForm please : https://forms.gle/Ruqfy9jTkWMALuDz9 



Complete and Continue  
Discussion

0 comments