Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Log file generation. #20

Closed
mfaisalkhatri opened this issue Oct 31, 2017 · 0 comments
Closed

Log file generation. #20

mfaisalkhatri opened this issue Oct 31, 2017 · 0 comments
Assignees
@WasiqB
Labels
severity: critical Issue is marked as critical. type: feature New feature being introduced.
Milestone
Version 2.1.0

Comments

@mfaisalkhatri
Copy link
Collaborator

Description

It is observed that in case of log file generation,Whenever a new Test is Run, system deletes the old log files and creates a fresh one.
In such a case, if user wants reference to old cases he has tested, he can't get as logs have already been deleted.
Hence, it is suggested to keep the old log files as it is and create a new file on every run.
Also, to overcome the name difficulty, appending Datetimestamp in the logfile name can be handy.

Environment

  • Appium server version: 1.7.1
  • Desktop OS version: Window 8.1
  • coteafs-appium version: 2.0.0.0
  • Mobile platform version: Android/4.4.2
  • Real device / simulator: Real Device
@WasiqB WasiqB self-assigned this Nov 2, 2017
@WasiqB WasiqB added type: feature New feature being introduced. severity: critical Issue is marked as critical. labels Nov 2, 2017
@WasiqB WasiqB added this to the Version 2.1.0 milestone Nov 2, 2017
@WasiqB WasiqB closed this as completed in 273bce3 Dec 5, 2017
WasiqB pushed a commit that referenced this issue Oct 2, 2018
Fixed #20, now it will generate new log file on every run by appendin…
6f00806 
…g date and index of the log file, e.g.: my-log-2017-11-16-1.log.**Note**: This will affect only framework logs and not Server logs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WasiqB WasiqB

Labels
severity: critical Issue is marked as critical. type: feature New feature being introduced.
Projects
None yet
Milestone
Version 2.1.0
Development

No branches or pull requests
2 participants
@WasiqB @mfaisalkhatri